Spare Parts Management and Reservation System

Abstract

Techniques for a spare part management and reservation system are provided. Based on a request received from a first client device, stored data indicating whether a part is available to a user is retrieved. A first indication is received from the first client device, the first indication including a request from the user to reserve the part in inventory. In response to data indicating the part is available to the user, a temporary reservation of the part for the user is generated and sent. A second indication is received from the first client device, the second indication including a notification indicating whether the part has been consumed by the user. In response to the notification indicating whether the part has or has not been consumed by the user, a real-time update of the temporary reservation is generated and sent, the real-time update including an indication of confirmation of the reservation or that the part is available for reservation.

Description

Background Art

[0001] Field service inventory management typically includes tracking and managing the storage, request, transfer, and consumption of inventory items (such as field service spare parts). For example, a combination of automated and manual processes can be used to track and manage parts inventory to record part usage, consumption, and returns; predict new part shipments; and facilitate part replenishment.

[0002] Modern field service inventory management systems can include spare parts management service (SMS) operations that automate previous manual processes, such as counting and recording each inventory item to fulfill part requests from field technicians. These systems can also implement in-stock optimization, product identification and tracking, part reordering / replenishment, and returns of defective or unused parts. For example, by leveraging various inventory tracking technologies, such as part identifiers (e.g., stock keeping unit (SKU), quick response (QR) code, serial number, or product number), smart storage cabinets, and forward (e.g., strategically distributed) inventory locations, SMS operations can provide users with real-time data on in-stock status (part availability) and enable inventory forecasting.

[0003] Inventory management systems that include SMS operations are typically part of a larger enterprise resource planning (ERP) system. The ERP system includes business management software that can implement integrated in-stock, accounting, point-of-sale, supply chain management, and other functions. Brief Description of the Drawings

[0004] From the following specification and drawings, various objectives, features, aspects, and advantages of the subject matter of the present invention will become more apparent, where like reference numerals represent like components.

[0005] Figure 1 A general overview diagram of a part reservation system based on an SMS portal according to an example is shown;

[0006] Figure 2A A flowchart of part reservation operations based on an SMS portal according to an example is shown;

[0007] Figure 2B A flowchart of part reservation operations based on an SMS portal according to an example is shown;

[0008] Figure 3A A flowchart of SMS portal operations from a client perspective according to an example is shown;

[0009] Figure 3B A flowchart of SMS portal operations from a server perspective according to an example is shown;

[0010] Figure 4Shows a graphical representation of the "Home" tab display of the SMS portal for inventory locations according to an example;

[0011] Figure 5 Shows a graphical representation of the "View Data Center" tab display of the SMS portal for available parts corresponding to inventory locations according to an example;

[0012] Figure 6 Shows a graphical representation of the "Create Part Request" tab display of the SMS portal for temporary part requests according to an example;

[0013] Figure 7 Shows a graphical representation of the "Manage Part Reservations" tab display of the SMS portal for part reservations according to an example;

[0014] Figure 8 Shows a graphical representation of the "Confirmed Orders" tab display of the SMS portal for confirmed part reservations according to an example;

[0015] Figure 9 Shows a graphical representation of the "View Inventory" tab display of the SMS portal for the in-stock status of part inventory according to an example;

[0016] Figure 10 Shows a block diagram of an exemplary client - server relationship that can be used to implement one or more aspects of various examples; and

[0017] Figure 11 Shows a block diagram of a distributed computer system that can be used to implement one or more aspects of various examples.

[0018] Although the examples are described with reference to the above - mentioned figures, the figures are intended to be illustrative, and other embodiments are in accordance with the spirit of the various examples and within their scope. Detailed Description

[0019] Field service inventory management systems generally include tracking, managing, and organizing the in - stock levels, orders, sales, and deliveries of parts. For example, such systems can be used to maintain optimal in - stock levels of parts, track parts during shipping / transportation to inventory locations, count and record parts, and record out - of - stock situations for individual parts.

[0020] As described above, computerized SMS operations can automate previous manual inventory management processes, such as taking an inventory count and recording of each inventory item to fulfill component requests from field technicians. SMS operations can also enable in-stock optimization, product identification and tracking, reordering capabilities, and return of unused components. For example, by leveraging various inventory tracking technologies such as component identifiers (e.g., stock keeping unit (SKU), quick response (QR) code, serial number, or product number), intelligent storage cabinets, and forward (e.g., strategically and / or geographically distributed) inventory locations, SMS operations can provide users with real-time data on in-stock status (component availability) and enable inventory forecasting and intelligent allocation functions.

[0021] Inventory management systems that include SMS hardware / software components are typically integrated (and / or coupled) with larger enterprise resource planning (ERP) systems. The ERP system includes business management hardware / software components that can implement functions such as integrating in-stock, accounting, point of sale, supply chain management, and other functions.

[0022] The component reservation system based on the SMS portal can also enable client device users (such as field technicians or engineers) to perform one or more functions via the SMS portal, including, for example, selecting an inventory location, viewing a real-time list of components corresponding to the inventory location, requesting a component, confirming and / or canceling a component reservation, and viewing the component in-stock status.

[0023] Although modern component reservation systems based on the SMS portal can achieve many inventory management objectives, these systems typically take a long time (up to 17 minutes in some cases) to process user / customer component reservation requests. This delay may be attributed to the waiting time of various back-end system operations in the critical path of the component reservation process (e.g., the waiting time for handshaking / coordination between the SMS portal-based component reservation system, the inventory order management system, the ERP system, and the accounting platform; file transfer protocol (FTP) conversion; warranty license check, or any other intermediate processing delay). For example, the current system can adopt batch processing jobs for component reservation requests, e.g., every 2 - 3 minutes, instead of direct links for individual component reservation requests, and may require handshaking to be completed between various order management systems before a request can be processed. Additionally, if a customer does not use a reserved component in a repair job, the current SMS portal-based component reservation system generally does not allow real-time coordination of ad-hoc component reservation requests. Instead, if a component is not used in a repair, it may have to be manually re-entered into the reservation system, e.g., as a return item.

[0024] The focus of the disclosed inventive subject matter is to implement an improved part reservation system based on a spare parts management service (SMS) portal. The SMS portal-based part reservation system disclosed herein coordinates inventory order management, enterprise resource planning (ERP), and a parts management platform to allow (1) real-time coordination of ad-hoc part reservation requests if a customer does not use a reserved part in a repair operation, and (2) part replenishment if a customer consumes a part. Such a system can include a combination of client / server software applications, supply chain logistics expertise, intelligent lockers, and physical inventory locations to timely deliver parts to meet service requests made by users (e.g., field technicians or engineers) when there is a demand for field service spare parts. Additionally, the present disclosure includes improvements in moving backend system operations out of the critical path of part reservation requests and allowing real-time visibility (improved accuracy) of inventory at physical inventory sites associated with customers, field reservation cancellation (backscan), and status updates (real-time inventory status) regarding incoming part replenishment / open deliveries. For example, the system can provide real-time information about part reservations, current and future part availability, and tracking data for parts in transit to inventory locations.

[0025] It should be understood that the disclosed technology provides many advantageous technical effects, including improving the efficiency and speed of part reservation operations based on the field SMS portal. It should also be recognized that the following description is not intended as an extensive overview, and thus, for clarity and conciseness, concepts may be simplified.

[0026] Figure 1 A general overview diagram of an SMS portal-based part reservation system according to one example is shown. The SMS portal-based part reservation system 100 includes a spare parts management service (SMS) 110; a plurality of client devices, such as client devices 120A - E, each configured with an SMS part reservation portal application, such as SMS part reservation portals 130A - E; an enterprise resource planning (ERP) system 140, and an inventory management system 150.

[0027] The SMS 110 includes an inventory order management platform configured to allow a user to reserve parts in inventory. As used herein, a part can include an item or service recorded in inventory. For example, inventory can include multiple parts and / or multiple types of parts stored in multiple physical locations to meet field service requests made by various users (e.g., field technicians or engineers). Items or services recorded in inventory through the inventory management system 150 are generally available to or accessible by certain users based on one or more criteria (e.g., a user's affiliation with an authorized consignor entity or inventory location, clearance levels, valid warranties, or other information).

[0028] As shown, SMS 110 includes at least one non-transitory memory, such as persistent storage device 112 and main storage device 114, on which computer-readable instructions are stored for implementing a component reservation system based on the SMS portal. The computer-readable instructions, when executed by at least one processor (e.g., processor(s) 116) coupled to the at least one memory, cause the at least one processor to perform at least one operation, as described in more detail below. Those skilled in the art will note that SMS 110 may also include other systems, subsystems, and / or components (e.g., display, keyboard, mouse, speakers, buttons, battery, fan, motherboard, power supply, etc.) for implementing the various component reservation operations described herein.

[0029] SMS 110 is electrically coupled to a plurality of client devices, such as client devices 120A-E, which are individually referred to herein as client device 120. Client device 120 includes at least one computing device, such as a cellular smartphone, information kiosk, personal data assistant, tablet computer, laptop computer, desktop computer, robot, vehicle, network camera, or other type of computing device. For example, client device 120 may be a mobile device assigned to a user (e.g., a field technician) that is configured to send and receive data communications to and from SMS 110, ERP system 140, and / or inventory management system 150 via a public or private cellular telecommunications network.

[0030] As shown, each client device 120 includes an SMS portal 130. For example, client devices 120A-E each include an SMS portal 130A-E, respectively. As described in detail below, SMS portal 130 is configured to allow technical improvements to a traditional SMS component reservation system, including: (1) real-time coordination of temporary component reservation requests, e.g., if a reserved component is not used by a user during a repair operation, and (2) on-site reservation cancellation (backscanning), e.g., if a component is not used during a repair operation. Thus, SMS portal 130 allows component reservations to be cancelled without manually re-entering the component into inventory management system 150 or performing other high-latency backend operations that are typically in the critical path of a component reservation request, e.g., the backend operations typically required for return items. Additionally, in various examples, SMS portal 130 may also allow for real-time visibility (improved accuracy) of inventory at a physical inventory site associated with a customer, as well as status updates regarding incoming component replenishments / open deliveries (real-time inventory status).

[0031] The ERP system 140 includes business management hardware / software components that allow for the integration of in-stock inventory, accounting, point-of-sale, supply chain management, and other functions. In some examples, the inventory management system 150 and / or the SMS 110 can be integrated subsystems of the ERP system 140 or can include stand-alone (e.g., proprietary) systems that communicate with the ERP system 140, as Figure 1 shown. In operation, the ERP 140 can be configured to coordinate business related to parts reserved from inventory via the SMS 110 and the inventory management system 150, facilitate replenishment of reserved parts, or perform various other back-end tasks related to overall inventory management or specifically related to part reservation. As described above, the various examples herein relate to improving various part reservation operations, including by moving certain high-latency back-end operations typically performed by the ERP system 140 out of the critical path for fulfilling part reservation requests.

[0032] The inventory management system 150 includes inventory management hardware / software components, such as a parts inventory database, that allow parts to be logged into inventory, checked out of inventory, returned to inventory, and / or other functions. The inventory management system 150 can be configured to manage parts inventory across multiple physical inventory locations. For example, the inventory management system 150 can include stored data that indicates that a part is available to a user at an inventory location associated with the user.

[0033] Although Figure 1 the SMS portal-based part reservation system shown in is exemplary for implementing the examples herein, those skilled in the art will understand that various other system architectures can be utilized (e.g., where the SMS 110 and / or the inventory management system 150 are integrated subsystems of the ERP system 140). Accordingly, the SMS portal-based part reservation system 100 should not be construed as strictly limited to the examples described herein.

[0034] It should also be noted that Figure 1The components in Figure 1 and the various functions attributed to each component are exemplary and are described only for purposes of ease of understanding. Those skilled in the art will understand that one or more of the functions attributed to the various components can be performed by any one of the other components and / or by components (not shown) configured to perform combinations of the various functions. Accordingly, it should be noted that any language referring to SMS 110, client device 120, SMS component reservation portal 130, ERP system 140, inventory management system 150, at least one processor 116, persistent storage device 112, or main storage device 114 should be understood to include any suitable combination of computing devices, including servers, interfaces, systems, databases, agents, peers, controllers, or other types of computing devices that operate alone or in combination to perform the functions attributed to the various components. Additionally, those skilled in the art will understand that one or more of the functions of the Figure 1 system described herein can be performed in the context of a client-server relationship, such as by one or more servers, one or more client devices (e.g., one or more user devices), and / or by a combination of one or more servers and client devices.

[0035] Figure 2A FIG. shows a flowchart of an SMS portal-based component reservation operation according to one example. As described above, SMS 110 can include at least one non-transitory memory, e.g., persistent storage device 112 and main storage device 114, on which computer-readable instructions are stored, e.g., for implementing the operations of flowchart 200, and the computer-readable instructions, when executed by at least one processor (e.g., (multiple) processors 116) coupled to the at least one memory, cause the at least one processor to perform the operations in flowchart 200.

[0036] For example, in step 210, based on a request received from a first client device (e.g., client device 120A), the SMS 110 may retrieve stored data indicating whether a component is available to the user from an inventory database (e.g., inventory management system 150), where the first client device is one of a plurality of client devices capable of accessing reserved components in the inventory. For example, the stored data indicating that the component is available to the user may include data indicating that the component is available at at least one inventory location associated with the user. For example, the inventory location may be associated with the user based on at least one of a vendor entity associated with the user or the geographical location of the user. Additionally, the stored data indicating that the component is available to the user may further include warranty information associated with the component, e.g., data indicating that the component that needs to be replaced is still within the warranty period. If the component is not available at the user's local inventory location, the SMS 110 may generate an offer and send it to the user (via the first client device) to initiate a confirmed order from a remote warehouse location. For example, the user may initiate a new request by checking the component serial number against the on-site assets and selecting the SKU (part number) of the component that the user wishes to replace. Then, the SMS 110 may generate an update and send it to the user (via the first client device), which shows whether the component is immediately available (reserved) or whether the component is being ordered from a remote warehouse location (order confirmation).

[0037] In step 220, the SMS 110 may receive a first indication from the first client device (e.g., client device 120A), the first indication including a request for a component in the reserved inventory from the user. In some examples, the first indication may include at least one of the following associated with the component: a short message service message, a stock keeping unit (SKU), a quick response (QR) code, a serial number, or a product number. For example, the user may initiate a reservation request for a component in the inventory by using the client device to scan and send a QR code pasted on the component (or pasted on the packaging associated with the component). Then, the scanned QR code and the identification data associated with the user and / or the client device may be received by the SMS 110 as the first indication including the request for a component in the reserved inventory from the user. In some examples, the first indication may include the user's selection of at least one inventory location associated with the user and / or the component.

[0038] In step 230, in response to data indicating a part is available to the user, SMS 110 can generate and send a provisional reservation of the part to at least one of a plurality of client devices (e.g., at least one of client devices 120A - E). As used herein, a provisional reservation is a reservation that depends on the part being consumed by the user at a later time. For example, a user may be required to perform a repair operation in which a defective part is identified as potentially needing replacement. Based on this initial assessment, the user can provisionally reserve the part through the SMS portal of the client device associated with the user, such that the part will be accessible if needed to complete the repair operation.

[0039] In step 240, SMS 110 can receive a second indication from a first client device, the second indication including a notification indicating whether the part has been consumed by the user (to the extent that it is no longer available in inventory in a repair scenario). For example, when the user begins a repair operation, the actual condition of the suspected defective part will become known, and at this time, the user will evaluate whether the part is truly needed to complete the repair. When making this evaluation, a user who has provisionally reserved the part through the SMS portal of the associated client device can also send, via the SMS portal of the client device associated with the user, a notification indicating whether the part has been consumed. In some examples, the second indication can include at least one of the following associated with the part: a short message service message, a stock - keeping unit (SKU), a quick response (QR) code, a serial number, or a product number. For example, the user can scan a QR code pasted on the part (or pasted on the packaging associated with the part) using the client device and send a second indication including the QR code and a notification indicating whether the part has been consumed. Then, SMS 110 can receive and process the second indication based on the notification.

[0040] Figure 2B A flowchart of an SMS - portal - based part reservation operation according to one example is shown. Continuing with flowchart 200, in step 250, SMS 110 can receive a notification indicating whether the part has been consumed by the user.

[0041] If the notification at step 250 indicates that the part has been consumed by the user, then in step 260, SMS 110 can generate and send a real - time update of the provisional reservation to at least one of a plurality of client devices, which includes the user's confirmed reservation of the part. For example, the SMS portal can be configured to receive a user - interface selection that allows the user to update the status of the provisional reservation and send the status update via SMS 110 to at least one other client device, such as one or more of client devices 120A - E, to notify different users associated with those devices that the part has been consumed and is no longer available for reservation.

[0042] In step 270, for example via the ERP system 140, the SMS 110 can further facilitate the replenishment of parts in inventory and coordinate the business related to the parts. For example, the SMS 110 can facilitate the replenishment of parts at the inventory location associated with the user. The SMS 110 can also send a communication to the ERP system 140 to coordinate the accounting process related to the part, such as by creating a settlement list to bill the appropriate merchant entity for the use of the part.

[0043] If the notification at step 250 indicates that the part has not been consumed by the user, then in step 280, the SMS 110 can generate and send a real-time update of the temporary reservation to at least one of the multiple client devices, which includes an indication that the part is available for reservation. In some examples, in response to the notification indicating that the part has not been consumed by the user, in step 290, the SMS 110 can facilitate the return of the part to inventory without initiating a Return Merchandise Authorization (RMA) process. For example, the SMS portal can be configured to receive a user interface selection that allows the user to update the status of the temporary reservation and send the status update to at least one other client device associated with a different user via the SMS 110. Additionally, the user who reserved the part can facilitate the return of the part to inventory by scanning the part back into inventory. For example, the user can return a good (non-defective) unused part via a portal or an application that is configured on the client device to provide access to the inventory management system 150. The inventory management system portal can allow the user to scan the unused part, such as a QR tracking number pasted on the unused part, and the scan can cause the inventory management system 150 to update the SMS portal 130 with the return status of the part, thereby automatically closing the open reservation.

[0044] Figure 3A and 3B A flowchart of a part reservation operation based on an SMS portal is shown from a client perspective and a server perspective, respectively, according to one example. For example, the SMS portal 130 configured on the client device 120 can be configured to perform Figure 3A one or more steps, while the SMS 110 can be configured to perform Figure 3B one or more steps. In some examples, as Figures 4 to 9 shown, the client device 120 and / or the SMS 110 can also be configured to generate and / or send to at least one of the multiple client devices the following: a first display element including the user's temporary reservation of a part, a second display element including at least one of the planned quantity or the real-time quantity of the part in inventory, a third display element including the real-time quantity of the temporarily reserved part, or a fourth display element including a tracking number of a part replenishment in transit to the inventory.

[0045] In flowchart 300, at step 310, the user identifies the need for a component. For example, the user / field engineer may be employed by or otherwise associated with the shipper entity to respond to a field service repair case, such as to repair an operating telecommunications system. According to an example herein, the shipper entity may issue a client device including an SMS portal to the user / field engineer, such as the client device 120 including the SMS portal 130 as described above. In response to a field service repair case (e.g., a work order related to a service interruption), the user / field engineer may identify that a component replacement may be needed to solve the problem. In this case, the client device 120 may be configured to allow the user / field engineer to access the SMS portal 130 to initiate a component reservation process based on the identified need. As Figure 4 shown, the SMS portal 130 may be configured to display a "Home" graphical user interface (GUI) to the user.

[0046] Figure 4 A graphical representation of an SMS portal "Home" tab display of inventory locations according to an example is shown. In display 400, the "Home" tab 410 allows access to the SMS portal, where the current open component reservation 420 and available inventory locations 430 are displayed for the user 440. For example, the available inventory locations may be displayed based on the user access level of the identified location (e.g., based on a location ID), geographical location (e.g., street, city, etc.), or other criteria. The tab 410 may also be configured to allow the user to select at least one inventory location for component reservation. For example, when the user identifies the need for a component, the user may select at least one inventory location for the available component, such as by selecting the indicator button 450 of the inventory location.

[0047] Figure 5 A graphical representation of an SMS portal "View Data Center" tab display of available components corresponding to an inventory location according to an example is shown. In display 500, after selecting at least one inventory location via the "Home" tab 410, the "View Data Center" tab 510 displays the available components at the selected inventory location(s). The display 500 may include various data related to the available components, such as serial number 520, product number 530, and location data 540 (e.g., location ID, street, city, site name, etc.). In addition, the "View Data Center" tab 510 may be configured to allow the user to initiate a component request via the selector button 550 associated with each component.

[0048] Figure 6Shows a graphical representation of the "Create Part Request" label display of the SMS portal for a temporary part request according to an example. In the display 600, after the user selects the part to be reserved via the selector button 550, the "Create Part Request" label 610 displays a part reservation form. For example, the part reservation form for the selected part may include various account details 620 (e.g., account name / contact, location, customer reference ID, etc.) and part details 630 (e.g., part number, organizational assignment, etc.). In addition, the label 610 may be configured to allow the user to select a temporary reservation 640 of the part for the repair case and to allow the user to select a confirmed reservation 650 indicating that the part has been consumed for the repair case. For example, once the temporary reservation selection is made, the label 610 also allows the user to submit 660 (or cancel 670) the part reservation order.

[0049] Return reference Figure 3A , after the user selects and submits a temporary reservation, at step 320, the SMS portal 130 generates a temporary reservation request for the part and sends it to the SMS 110. If the part is immediately available, at step 330, the SMS portal 130 further allocates the part. For example, the SMS portal 130 may access an inventory database via the SMS 110, which indicates that the part is in stock at a physical inventory location near the user / field engineer's location. Based on the indicated availability and the reservation request, the SMS portal 130 may generate or update an entry in the inventory database to reflect that the part has been allocated to the user / field engineer (reserved for their use).

[0050] From Figure 3B From the server-side perspective 340 shown, after receiving the temporary reservation request for the part, at step 345, the SMS 110 generates a temporary reservation update and sends it to at least one of the multiple client devices, e.g., at least one of the client devices 120A-E. For example, when the temporary reservation request is received from the user / field engineer's client device, the SMS 110 may generate a temporary reservation update. Then, the SMS 110 may send the temporary reservation update in real time to the client devices associated with other users. For example, the temporary reservation update of the part may be displayed in the SMS portal of at least one client device associated with another user.

[0051] Figure 7Shows a graphical representation of the "Manage Part Reservation" label display 700 of the SMS portal for part reservation according to an example. Label 710 shows a summary of part reservation data, including, for example, creation date 720, inventory location data 730, assigned case number 740, customer (shipper entity) reference ID number / assigned user 750, part identification data 760, real-time local stock data 770, and real-time reservation / part status data 780. For example, the real-time reservation / part status data 780 can indicate that the part reservation has been cancelled (and by whom), the reservation is open (current) and the selected part is ready for collection, or other descriptive information. In addition, label 710 can also allow the user to cancel 790 an open part reservation order.

[0052] Return reference Figure 3A , at step 350, the user can scan the selected part in the inventory to complete the repair case. For example, the client device 120 can also include a camera and / or barcode scanner configured to scan and read (e.g., from the box or label of the part) at least one of the stock keeping unit (SKU), quick response (QR) code, serial number, or product number associated with the part. The scanned or read information can then be recorded via the SMS portal 130, e.g., locally at the client device, or remotely via transmission to the SMS 110. After scanning the part from the inventory, the user can physically remove the part from the inventory to complete the repair case.

[0053] Figure 8 Shows a graphical representation of the "Confirm Order" label display 800 of the SMS portal for confirming part reservation according to an example. Label 802 shows information related to confirming the part reservation, including, for example, reservation date 804, inventory location 806, case number 808, customer (shipper entity) reference ID number / assigned user 810, part identification data 812, real-time local stock data 814, and real-time reservation / part status data 816, as well as part description 818.

[0054] From Figure 3A the client-side perspective, if the part is not used in the repair case at decision 360, then at step 370, the user can scan the part back into the inventory. For example, after physically removing the part from the inventory and starting the repair job, the user may find that the part currently in use is not damaged or defective, or the root cause of the problem is not the part currently in use. In such a case, the user can determine that the part removed from the inventory is not needed and can put it back into the inventory for future reservation by other users.

[0055] Once the part is scanned back into inventory, the SMS portal 130 can generate a temporary reservation update and send it to the SMS 110, which indicates that the part is open for reservation. In some examples, the SMS 110 can generate a temporary reservation update and send it to at least one of the multiple client devices, such as at least one of the client devices 120A-E.

[0056] Return reference Figure 8 The label 802 can allow the user to add defect return / return tracking information 820. For example, when scanning a part back into inventory, the user can further indicate that a reserved part not used in a repair case is defective and is, for example, returned to the part manufacturer or supplier.

[0057] Return reference Figure 3B From the server-side perspective 380, if it is determined at 360 that the part is used in a repair case, then at step 385, the SMS 110 generates a temporary reservation confirmation and sends it to at least one of the multiple client devices, such as at least one of the client devices 120A-E. For example, after physically removing the part from inventory and starting a repair job, the user may find that the part currently in use is damaged or defective. In such a case, the user can complete the repair by replacing the part currently in use with the reserved part.

[0058] After confirming that the part has been consumed, the temporary reservation confirmation of the part can be displayed in the SMS portal of at least one client device. Additionally, at step 390, the SMS 110 can update the repair case details and / or facilitate the coordination of the business associated with the part, for example, via the ERP system 140.

[0059] Figure 9 Shows a graphical representation of the "View Inventory" label display 900 of the SMS portal for the in-stock status of parts according to an example. The label 910 displays the inventory status information of the selected part 920 at the inventory location 930, including, for example, the number of available parts at the inventory location 940, the planned shipment quantity 950, the reservation status 960 of the selected part, the number of parts in transit 970, and the (multiple) tracking ID 980 of the parts in transit. For example, once the part is consumed, the user can access the label 910 to check the real-time status and availability of the selected incoming part at the selected inventory location based on, for example, real-time updates received from the SMS 110.

[0060] Figure 10A high-level block diagram of an exemplary client-server relationship that can be used to implement the systems, devices, and methods described herein is shown. The client-server relationship 1000 includes a client device 1010 communicating with a server 1020 via a network 1030, and shows Figure 2A , 2B a possible division of the method steps of 3A and 3B between the client device 1010 and the server 1020.

[0061] For example, at step 1040, according to the various examples above, the client device 1010 may generate and send a first indication that includes a request for a part in the reserved inventory from the user. For example, the user may initiate a reservation request for a part in the inventory by using the client device 1010 to scan and send a QR code pasted on the part (or pasted on the packaging associated with the part). At step 1042, in response to data indicating that the part is available to the user, the client device 1010 may also receive a temporary reservation of the part by the user. For example, the client device 1010 may receive a temporary reservation of the part generated and sent by the server 1020. At step 1044, the client device 1010 may also generate and send a second indication that includes a notification indicating whether the part has been consumed by the user. For example, the user may use the client device 1010 to scan a QR code pasted on the part (or pasted on the packaging associated with the part) and send a second indication to the server 1020 that includes the QR code and a notification indicating whether the part has been consumed.

[0062] In response to the notification indicating that the part has been consumed by the user at step 1046, at step 1048, the client device 1010 may also receive a real-time update of the temporary reservation from the server 1020, which includes the user's confirmed reservation of the part. The confirmed reservation may notify the user of the client device 1010 and different users associated with other client devices that the part has been consumed and is no longer available for reservation.

[0063] In response to the notification indicating that the part has not been consumed by the user at step 1046, at step 1050, the client device 1010 may also receive a real-time update of the temporary reservation from the server 1020, which includes an indication that the part is available for reservation. At step 1052, the client device 1010 may facilitate the display of the real-time update of the temporary reservation.

[0064] Based on a request received from a first client device (e.g., client device 1010), at step 1060, server 1020 may retrieve stored data indicating whether a part is available to a user from at least one inventory database, where the first client device is one of a plurality of client devices capable of accessing to reserve parts in inventory. For example, the stored data indicating the part is available to the user may include data indicating the part is available at at least one inventory location associated with the user. Alternatively, if the part is not available at an inventory location local to the user, server 1020 may generate an offer and send it to the user (via the first client device) to initiate a confirmed order from a remote warehouse location.

[0065] At step 1062, server 1020 may also receive a first indication from the first client device (e.g., client device 1010), the first indication including a request from the user to reserve the part in inventory. In some examples, the first indication may include a selection by the user of at least one inventory location associated with the user and / or the part. In response to data indicating the part is available to the user, at step 1064, server 1020 may also generate a temporary reservation of the part for the user and send it to at least one of the plurality of client devices. For example, server 1020 may generate the temporary reservation after receiving a temporary reservation request from the first client device (e.g., client device 1010). Then, server 1020 may send the temporary reservation to other client devices in real time. At step 1066, server 1020 may also receive a second indication from the first client device, the second indication including a notification indicating whether the part has been consumed by the user.

[0066] In response to the notification indicating the part has been consumed at step 1068, at step 1070, server 1020 may also generate and send to at least one of the plurality of client devices a real-time update of the temporary reservation, the real-time update including a confirmed reservation of the part for the user. For example, the confirmed reservation may notify the user of the first client device (client device 1010) and different users associated with other client devices that the part has been consumed and is no longer available for reservation.

[0067] In response to the notification indicating that the component has not been consumed by the user at step 1068, at step 1072, the server 1020 may also generate and send a real-time update of the temporary reservation to at least one of the multiple client devices, and the real-time update includes an indication that the component is available for reservation. For example, a user who reserves a component can facilitate the return of the component to inventory by scanning the component back into inventory. In some examples, in response to the notification indicating that the component has not been consumed by the user, the server 1020 may facilitate the return of the component to inventory without initiating a Return Merchandise Authorization (RMA) process.

[0068] Those skilled in the art will understand that Figure 10 the exemplary client-server relationship shown in is only one of many client-server relationships that can be used to implement the systems, apparatuses, and methods described herein. Thus, Figure 10 the client-server relationship shown in should not be construed as a limitation in any way. Examples of client devices 1010 may include cellular smartphones, information query terminals, personal data assistants, tablet computers, laptop computers, desktop computers, robots, vehicles, network cameras, or other types of computing devices.

[0069] The systems, apparatuses, and methods described herein can be implemented using a computer program product tangibly embodied in an information carrier, such as in a non-transitory machine-readable storage device, for execution by a programmable processor; and the method steps described herein, including one or more of the method steps described herein, can be implemented using one or more computer programs executable by such a processor. A computer program is a set of computer program instructions that can be used directly or indirectly in a computer to perform a certain activity or produce a certain result. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0070] Figure 11A high-level block diagram of an exemplary apparatus that can be used to implement the systems, devices, and methods described herein is shown. Apparatus 1100 includes a processor 1110 operatively coupled to a permanent storage device 1120 and a main storage device 1130. The processor 1110 controls the overall operation of the apparatus 1100 by executing computer program instructions that define the operation of the apparatus 1100. The computer program instructions can be stored in the permanent storage device 1120 or other computer-readable media and are loaded into the main storage device 1130 when the computer program instructions need to be executed. For example, SMS 110, multiple client devices 120, ERP system 140, and inventory management system 150 can include one or more components of computer 1100. Thus, the various method steps herein can be defined by computer program instructions stored in the main storage device 1130 and / or the permanent storage device 1120 and controlled by the processor 1110 that executes the computer program instructions. For example, the computer program instructions can be implemented as computer-executable code programmed by those skilled in the art to execute the algorithms defined by the method steps herein. Thus, by executing the computer program instructions, the processor 1110 executes the algorithms defined by the method steps herein. Additionally or alternatively, the instructions for implementing the method steps herein according to the disclosed examples can reside in a computer program product 1150. When the processor 1110 executes the instructions of the computer program product 1150, the instructions or a portion thereof are typically loaded into the main storage device 1130, and the processor 1110 can easily access the instructions from the main storage device 1130.

[0071] Apparatus 1100 also includes one or more network interfaces 1180 for communicating with other devices via a network. Apparatus 1100 can also include one or more input / output devices 1190 (e.g., a display, keyboard, mouse, speakers, buttons, etc.) that allow a user to interact with the apparatus 1100.

[0072] The processor 1110 can include a general-purpose microprocessor and a special-purpose microprocessor and can be the sole processor of the apparatus 1100 or one of multiple processors. The processor 1110 can include one or more central processing units (CPUs) and one or more graphics processing units (GPUs), which, for example, can work separately and / or multitask with one or more CPUs to accelerate processing, such as for various image processing applications described herein. The processor 1110, the permanent storage device 1120, and / or the main storage device 1130 can include, be supplemented with, or incorporate one or more application-specific integrated circuits (ASICs) and / or one or more field-programmable gate arrays (FPGAs).

[0073] The permanent storage device 1120 and the main storage device 1130 each include a tangible non-transitory computer-readable storage medium. The permanent storage device 1120 and the main storage device 1130 each may include high-speed random access memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), double data rate synchronous dynamic random access memory (DDR RAM), or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, such as internal hard disks and removable disks, magneto-optical storage devices, optical disk storage devices, flash memory devices, semiconductor storage devices, such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), digital versatile disc read-only memory (DVD-ROM) discs, or other non-volatile solid-state storage devices.

[0074] The input / output device 1190 may include peripheral devices, such as printers, scanners, display screens, etc. For example, the input / output device 1190 may include a display device for displaying information to a user (e.g., DNA accessibility prediction results), such as a cathode ray tube (CRT), plasma, or liquid crystal display (LCD) monitor, a keyboard, and a pointing device such as a mouse or trackball, through which the user may provide input to the apparatus 1100.

[0075] Any and all systems and apparatuses discussed herein, including the SMS 110, the plurality of client devices 120, the ERP system 140, and the inventory management system 150, may be executed by and / or incorporated into an apparatus such as the apparatus 1100. Additionally, the apparatus 1100 may utilize one or more neural networks or other deep learning techniques to execute the SMS 110, the plurality of client devices 120, the ERP system 140, the inventory management system 150, or other systems or apparatuses discussed herein.

[0076] Those skilled in the art will recognize that the implementation of an actual computer or computer system may have other structures and may also include other components (e.g., batteries, fans, motherboards, power supplies, etc.), and Figure 11 is a high-level representation of some components of such a computer for illustrative purposes.

[0077] This document describes various examples with reference to the accompanying drawings, which form a part of this document and illustrate specific ways of implementing the examples by way of illustration. However, this specification can be implemented in many different forms and should not be construed as limited to the examples set forth herein; rather, these examples are provided so that this specification will be thorough and complete and will fully convey the scope of the examples to those skilled in the art. Among other things, this specification can also be implemented as a method or a device. Thus, any one of the various examples herein can take the form of a complete hardware example, a complete software example, or an example combining software and hardware aspects. Therefore, this specification should not be construed in a limiting sense.

[0078] Throughout the specification and claims, the following terms have the meanings explicitly associated herein, unless the context clearly indicates otherwise:

[0079] The phrase "in one example" as used herein does not necessarily refer to the same example, although it can. Thus, as described above, various examples can be readily combined without departing from their scope or spirit.

[0080] As used herein, unless the context clearly indicates otherwise, the term "or" is an inclusive "or" operator and is equivalent to the term "and / or".

[0081] The term "based on" is not exclusive and allows for additional factors not described, unless the context clearly indicates otherwise.

[0082] As used herein, unless the context indicates otherwise, the term "coupled to" is intended to include both direct coupling (where two elements that are coupled together are in contact with each other) and indirect coupling (where at least one additional element is located between the two elements). Thus, the terms "coupled to" and "coupled with" are used synonymously. In the context of a networking environment where two or more components or devices are capable of exchanging data, the terms "coupled to" and "coupled with" are also used to mean "communicatively coupled with", possibly via one or more intermediate devices.

[0083] Furthermore, throughout the specification, the meanings of "a", "an", and "the" include plural referents, and the meaning of "in" includes "in" and "on".

[0084] Although some of the various examples presented herein constitute a single combination of creative elements, it should be understood that the subject matter of the present invention is considered to include all possible combinations of the disclosed elements. Thus, if one example includes elements A, B, and C, and another example includes elements B and D, the subject matter of the present invention is considered to include the other remaining combinations of A, B, C, or D, even if not explicitly discussed herein. Additionally, the transitional term "comprising" means having parts or members, or as such parts or members. As used herein, the transitional term "comprising" is inclusive or open-ended and does not exclude additional, unrecited elements or method steps.

[0085] In the foregoing discussion, reference has been made several times to servers, services, interfaces, clients, peers, portals, platforms, or other systems formed by computing devices. It should be understood that the use of these terms is considered to represent one or more computing devices having at least one processor (e.g., ASIC, FPGA, DSP, x86, ARM, ColdFire, GPU, multi-core processor, etc.) configured to execute software instructions stored on a computer-readable tangible, non-transitory medium (e.g., hard disk drive, solid state drive, RAM, flash memory, ROM, etc.). For example, a server may include one or more computers operating as a web server, database server, or other type of computer server in a manner that fulfills the described roles, responsibilities, or functions. It should also be understood that the disclosed computer-based algorithms, processes, methods, or other types of instruction sets may be implemented as a computer program product that includes a non-transitory, tangible computer-readable medium storing instructions that cause a processor to execute the disclosed steps. Various servers, systems, databases, or interfaces may exchange data using standardized protocols or algorithms, possibly based on HTTP, HTTPS, AES, public-private key exchange, web service APIs, known financial transaction protocols, or other methods of electronic information exchange. Data exchange may occur over packet-switched networks, circuit-switched networks, the Internet, LANs, WANs, VPNs, or other types of networks.

[0086] As used in the description herein and in the subsequent claims, when a system, server, device, or other computing element is described as being configured to perform or execute a function on data in a memory, the meaning of "configured to" or "programmed to" is defined as one or more processors or cores of a computing element programmed by a set of software instructions stored in the memory of the computing element to perform a set of functions on target data or data objects stored in the memory.

[0087] It should be noted that any language for a computer should be understood to include any suitable combination of computing devices, including servers, interfaces, systems, databases, agents, peers, controllers, or other types of computing devices that operate alone or in concert. It should be understood that a computing device includes a processor configured to execute software instructions stored on a tangible, non-transitory computer-readable storage medium (e.g., hard disk drive, FPGA, PLA, solid state drive, RAM, flash memory, ROM, etc.), and may include various other components such as batteries, fans, motherboards, power supplies, etc. The software instructions configure or program the computing device to provide roles, responsibilities, or other functions as discussed below with respect to the disclosed apparatus. Additionally, the disclosed technology may be implemented as a computer program product that includes a non-transitory computer-readable medium storing software instructions that cause a processor to perform the disclosed steps associated with the implementation of computer-based algorithms, processes, methods, or other instructions. In some examples, various servers, systems, databases, or interfaces use standardized protocols or algorithms to exchange data, possibly based on HTTP, HTTPS, AES, public-private key exchange, web service APIs, or other methods of electronic information exchange. Data exchange between devices can occur over packet-switched networks, the Internet, LANs, WANs, VPNs, or other types of packet-switched networks; circuit-switched networks; cell-switched networks, or other types of networks.

[0088] The foregoing specification is to be understood in every aspect as illustrative and exemplary, and not restrictive, and the scope of the examples disclosed herein is not determined from the specification, but rather from the claims according to the full breadth of interpretation permitted by patent law. It should be understood that the examples shown and described herein are merely illustrative of the principles of the present disclosure, and that various modifications can be implemented by those skilled in the art without departing from the scope and spirit of the present disclosure. Those skilled in the art can implement various other combinations of features without departing from the scope and spirit of the present invention.

Claims

1. A system, comprising: at least one memory storing computer-readable instructions that, when executed by at least one processor coupled to the at least one memory, cause the at least one processor to: retrieve the status availability of components in inventory from at least one inventory database; determine that a user associated with a first client device is one of a plurality of client devices that can access reserved components in the inventory; receive, from the first client device, a request to reserve the component in the inventory; generate a temporary reservation for the component in response to the status availability of the component indicating that the component is available to the user and determining that the user associated with the first client device can access reserved components in the inventory; send the temporary reservation to at least one of the plurality of client devices; generate a confirmed reservation for the component in response to determining that the component has been consumed by the user, the confirmed reservation identifying a real-time update to the temporary reservation of the component, and send the confirmed reservation to at least one of the plurality of client devices; and generate an indication that the component is available for reservation in response to determining that the component has not been consumed by the user within a time threshold for generating the temporary reservation of the component.

2. The system according to claim 1, when determining that the component has been consumed by the user, further causing the at least one processor to: facilitate replenishment of the component in the inventory; and coordinate operations associated with the replenishment.

3. The system according to claim 1, when determining that the component has not been consumed by the user within the time threshold for generating the temporary reservation of the component, by: receiving a scan of the component from the first client device; updating the inventory to identify the availability of the reservation for the component; and sending the indication that the component is available for reservation.

4. The system according to claim 2, wherein facilitating replenishment of the component in the inventory adds the component at an inventory location associated with the user.

5. The system according to claim 1, wherein the request associates the geographical location of the user with at least one location of the component in the inventory.

6. The system according to claim 1, wherein the at least one processor is further caused to generate at least one of the following: a first display element including the user's temporary reservation of the component; a second display element including at least one of a planned quantity or a real-time quantity of the component in the inventory; a third display element including the real-time quantity of the component associated with the temporary reservation; or a fourth display element including a tracking number for replenishment of the component to the inventory.

7. The system according to claim 1, wherein the request includes at least one of the following associated with the component: a Short Message Service message, a Stock Keeping Unit (SKU), a Quick Response (QR) code, a serial number, or a product number.

8. The system according to claim 1, wherein the system determines that the user can access the reserved component in the inventory based on one or more of the user's subordination relationship with the inventory location, the permission level, and the effective warranty.

9. The system according to claim 1, wherein the user associated with the first client device capable of accessing the reserved component in the inventory is a field technician.

10. The system according to claim 1, wherein the temporary reservation is cancelled based on the end time of the repair operation, without manually re-entering the component into the inventory.

11. The system according to claim 1, wherein the at least one processor is further caused to: automatically create a settlement list to bill the shipper entity for the use of the component in response to the real-time update of the temporary reservation and the generation of the confirmed reservation.

12. The system according to claim 1, wherein the at least one processor is further configured to: add warranty information indicating that the component is within the warranty period when generating the temporary reservation of the component.

13. A computerized method, comprising: retrieving the status availability of components in an inventory from at least one inventory database; determining that a user associated with a first client device is one of a plurality of client devices capable of accessing reserved components in the inventory; receiving, from the first client device, a request to reserve the component in the inventory; generating a temporary reservation of the component in response to the status availability of the component indicating that the component is available to the user and determining that the user associated with the first client device can access reserved components in the inventory; sending the temporary reservation to at least one of the plurality of client devices; generating a confirmed reservation of the component in response to determining that the component has been consumed by the user, the confirmed reservation identifying a real-time update of the temporary reservation of the component, and sending the confirmed reservation to at least one of the plurality of client devices; and generating an indication that the component is available for reservation in response to determining that the component has not been consumed by the user within a time threshold of generating the temporary reservation of the component.

14. The method according to claim 13, further comprising: facilitating replenishment of the component in the inventory; and coordinating the operations associated with the replenishment.

15. The method according to claim 14, wherein facilitating replenishment of the component in the inventory adds the component at an inventory location associated with the user.

16. The method according to claim 13, wherein the request associates the geographical location of the user with at least one location of the component in the inventory.

17. The method according to claim 13, further comprising: Generate a display element, the display element including at least one of the following: the user's temporary reservation of the component, the planned quantity or real-time quantity of the component in the inventory, the real-time quantity of the component associated with the temporary reservation, or the replenishment of the component in transit to the inventory.

18. The method according to claim 13, wherein the request includes at least one of the following associated with the component: a short message service message, a stock keeping unit (SKU), a quick response (QR) code, a serial number, and a product number.

19. A computer program product having computer-readable instructions stored thereon, the computer-readable instructions, when executed by at least one processor, cause the at least one processor to perform one or more steps, the steps including: Retrieve the status availability of components in an inventory from at least one inventory database; Determine that a user associated with a first client device is one of a plurality of client devices capable of accessing reserved components in the inventory; Receive, from the first client device, a request to reserve the component in the inventory; In response to the status availability of the component indicating that the component is available to the user and determining that the user associated with the first client device is capable of accessing reserved components in the inventory, generate a temporary reservation of the component; Send the temporary reservation to at least one of the plurality of client devices; In response to determining that the component has been consumed by the user, generate a confirmed reservation of the component, the confirmed reservation identifying a real-time update to the temporary reservation of the component, and send the confirmed reservation to at least one of the plurality of client devices; And In response to determining that the component has not been consumed by the user within a time threshold of generating the temporary reservation of the component, generate an indication that the component is available for reservation.

Images