The present invention relates to methods and systems of maintaining inventory systems for power tool devices, and generating reports for power tool devices.
In one embodiment, the invention provides a method of adding a power tool device to an inventory list. The method includes receiving, via a user interface, a request to add a nearby power tool device and receiving, via a short-range transceiver, identification from a plurality of power tool devices. The method also includes displaying, via the user interface, the identification information of the plurality of power tool device and receiving, via the user interface, a selection of a power tool device from the plurality of power tool devices. The method further includes adding, using a processor, the power tool device to the inventory list.
In one embodiment, the invention provides a method of analyzing metrics for a power tool device. The method includes receiving, via a short-range transceiver, identification signals from a plurality of power tool devices and displaying, via a user interface, identification information of the plurality of power tool devices. The method also includes receiving, via the user interface, a selection of a power tool device to be analyzed from the plurality of power tool devices and receiving, via the short-range transceiver, metrics information regarding the power tool device in response to the selection of the power tool device to be analyzed. The method further includes displaying, via the user interface, metrics information of the power tool device.
In one embodiment, the invention provides a method for determining power tool attendance. The method includes receiving a list of a first plurality of power tools and receiving, via a user interface, a selection to detect nearby tools. The method also includes receiving, via a short-range transceiver, identification signals from a second plurality of power tools and determining, using a processor, that a subset of the first plurality of power tools is missing based on the identification signals. The method further includes generating, using the processor, an indication that the subset of the first plurality of power tools is missing.
In one embodiment, the invention provides a communication system including a communicating power tool device and a non-communicating power tool device. The communicating power tool device can communicate wirelessly with a mobile external device. The mobile external device including a processor configured to receive information from an external server regarding the communicating power tool device, receive information from the user regarding the non-communicating power tool device, and group the communicating power tool wireless device and the non-communicating power tool device together as a single inventory.
In another embodiment the invention provides a method of determining whether any power tool devices are missing from an inventory. The method includes receiving a list of power tool devices from a remote server, directly communicating with a plurality of power tool devices, generating a list of the plurality of power tool devices; comparing the list of power tool devices received from the remote server and the plurality of devices, and determining whether a power tool device is missing.
Other aspects of the invention will become apparent by consideration of the detailed description and accompanying drawings.
Before any embodiments of the invention are explained in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. The invention is capable of other embodiments and of being practiced or of being carried out in various ways.
It should be noted that a plurality of hardware and software based devices, as well as a plurality of different structural components may be utilized to implement the invention. Furthermore, and as described in subsequent paragraphs, the specific configurations illustrated in the drawings are intended to exemplify embodiments of the invention and that other alternative configurations are possible. The terms “processor” “central processing unit” and “CPU” are interchangeable unless otherwise stated. Where the terms “processor” or “central processing unit” or “CPU” are used as identifying a unit performing specific functions, it should be understood that, unless otherwise stated, those functions can be carried out by a single processor, or multiple processors arranged in any form, including parallel processors, serial processors, tandem processors or cloud processing/cloud computing configurations.
As shown in
The memory 113 of the wireless communication module 109 can store data related to communications between the power tool 104 and the mobile electronic device 108. The processor 115 for the wireless communication module 109 controls wireless communications between the power tool 104 and the mobile electronic device 108. For example, the processor 115 associated with the wireless communication module 109 buffers incoming and/or outgoing data, communicates with the controller 118 of the power tool device 104, and determines the communication protocol and/or settings to use in wireless communications. The wireless communication module 109 receives electrical power from the main power source 119 and from the secondary power supply (e.g., back-up power supply 110) based on which power supply is available. When the main power source 119 is connected to the power tool device 104 and the main power source 119 holds sufficient power, the main power source 119 provides electrical power to the wireless communication module 109. If, on the other hand, the main power source 119 is not connected to the power supply, the back-up power supply 110 provides power to the wireless communication module 109. The back-up power supply 110, however, has limited supply of power and could be quickly drained if used to power significant electronic data exchange between the power tool devices 104 and the mobile electronic device 108. Therefore, in some embodiments, when the back-up power supply 110 powers the wireless communication module 109, the power tool device 104 outputs (e.g., broadcasts) only identification information for the power tool device 104, but does not enable further data exchange between the power tool device 104 and the mobile electronic device 108.
In some embodiments, the back-up power supply is a coin cell battery. The coin cell battery is removable from the power tool device 104 and is, therefore, located in an accessible area of the power tool device 104. In many embodiments, the back-up power supply 110 is accessed and replaced by the user/operator of the power tool device 104. In other embodiments, however, the back-up power supply 110 is located in a hard-to-access portion of the power tool device, and is replaced by a professional serviceman. For instance, rather than being located in a dedicated battery recess separate from the motor and other circuitry and accessible via a sliding or removable door on the tool housing, the back-up power supply 110 may require opening the main housing using one or more tools.
In the illustrated embodiment, the wireless communication module 109 is a Bluetooth® controller. The Bluetooth® controller communicates with the mobile electronic device 108 employing the Bluetooth® protocol. Therefore, in the illustrated embodiment, the mobile electronic device 108 and the power tool 104 are within a communication range (i.e., in proximity) of each other while they exchange data. In other embodiments, the wireless communication module 109 communicates using other protocols (e.g., Wi-Fi, cellular protocols, etc.) over a different type of wireless networks. For example, the wireless communication module 109 may be configured to communicate via Wi-Fi through a wide area network such as the Internet or a local area network, or to communicate through a piconet (e.g., using infrared or NFC communications). The communication via the communication module 109 may be encrypted to protect the data exchanged between the power tool 104 and the mobile electronic device 108 from third parties.
The RTC 117 increments and keeps time independently of the other power tool components. In the illustrated embodiment, the RTC 117 is powered through the wireless communication module 109 when the wireless communication module 109 is powered. In some embodiments, however, the RTC 117 is a separate component from the wireless communication module 109. In such embodiments, the RTC 117 receives power from the main power source 119 when the battery pack is connected to the power tool 104 and receives power from the back-up power supply 110 when the battery pack is not connected to the power tool 104. Therefore, the RTC 117 keeps track of time regardless of whether the power tool 104 is in operation, and regardless of whether the battery pack is connected to the power tool 104. When no power source is present (i.e., the battery pack is detached from the power tool 104 and the back-up power supply 110 is removed or depleted), the RTC 117 stores the last valid time. When a power source is replaced (i.e., the battery pack is attached to the power tool 104 or/and the coin cell 110 is replaced), the RTC 117 uses the stored time as a starting point to resume keeping time.
Other power tool devices (e.g., power tool 104d), however, do not communicate with the mobile electronic device 108, and therefore do not include the wireless communication module 109. In some embodiments, some of the power tool devices may include a wireless communication module 109, but may not be configured to communicate with the mobile electronic device 108 because, for example, the wireless communication module 109 utilizes a different communication protocol, and/or the power tool device 104 does not know how to interpret the instructions from the mobile electronic device 108.
In some embodiments, the mobile electronic device 108 is a dedicated electronic device. In other words, the mobile electronic device 108 is specifically manufactured to communicate with the power tool devices 104 and the remote server 112. In some embodiments, the dedicated electronic device may include a ruggedized exterior to withstand the environmental conditions of different worksites.
In other embodiments, the mobile electronic device 108 is not a dedicated electronic device and is configured to perform various functions not related to communicating with power tools 104. For example, the mobile electronic device 108 may be configured to place phone calls, play videos, share media, etc. The mobile electronic device 108 may be, for example, a laptop computer, a tablet computer, a smartphone, a cellphone, a personal digital assistant (PDA), or another electronic device capable of communicating wirelessly with the communicating power tool devices 104a-c and providing a graphical user interface.
The communicating power tool devices 104a-c may communicate power tool status, power tool operation statistics, power tool identification, stored power tool usage information, power tool maintenance data, battery pack identification, battery pack stored voltage, battery pack charge and discharge characteristics, and the like to the mobile electronic device 108. Therefore, by using the mobile electronic device 108, a user can access stored power tool device usage or power tool device maintenance data. The mobile electronic device 108 can also transmit data to each of the communicating power tool devices 104a-c for power tool configuration, firmware updates, or to send commands (e.g., turn on work light). The mobile electronic device 108 also allows a user to set operational parameters, safety parameters, select operating modes, and the like for the communicating power tool devices 104a-c.
The mobile electronic device 108 can also establish wireless communication with the remote server 112 through the network 114. The mobile electronic device 108 can forward to the remote server 112 at least some of the information received from the communicating power tool devices 104a-c. For example, the mobile electronic device 108 can forward new user-defined tool modes, power tool usage information, new identification information, power tool device status, and the like. The remote server 112 provides additional storage and processing power and thereby enables the communication system 100 to encompass more power tool devices 104a-d without being limited to the storage and processing capabilities of the mobile electronic device 108. Furthermore, the remote server 112 can also communicate with the external device 116 through the network 114 or through a different network to provide additional functionality.
The external device 116 may be, for example, a laptop computer, a desktop computer, a workstation from a local network, or another device configured to communicate with the remote server 112 through the network 114. The remote server 112 can forward the information received from the mobile electronic device 108 to the external device 116 through the network 114. Forwarding the information allows other users, who may, for example, be at a remote location from the power tool devices 104a-d and the mobile electronic device 108, to receive information regarding various parameters, characteristics, and status of the power tool devices 104a-d. The external device 116 can also generate and send new information to update data on the server 112, the mobile electronic device 108, and the communicating power tool devices 104a-c. For example, the external device 116 can assign locations for the specific tool devices, and the like.
In some implementations, the power tool devices 104a-d are owned by a larger entity (e.g., a contracting company). The larger entity then allows specific users (e.g., operators) to use the power tool devices 104a-d to perform specific tasks related to a project. Establishing the communication system 100 between power tool devices 104a-d and the electronic devices 108, 112, 116 allows individual users and/or larger entities to accurately control, manage, maintain, and operate large groups of power tool devices without cumbersome tracking, inventory, and programming methods.
In particular, the communication system 100 implements an inventory system. The inventory system provides information regarding the number of power tool devices 104a-d in the communication system 100, the location of the power tool devices 104a-d, the status of the power tool devices 104a-d, the purchasing information of the power tool devices 104a-d, and the like. The inventory information gathered and provided by the inventory system allows users (e.g., buyers) to buy desired and/or necessary tool devices, arrange for maintenance of tool devices, and track the power tool devices 104a-d.
For the inventory system, the server 112 stores an inventory database 145 (as shown in
Both the mobile electronic device 108 and the external device 116 execute the inventory system and provide desired information to the user. The mobile electronic device 108 and the external device 116 are able to synchronize the inventory information by communicating with the remote server 112 through the network 114. Therefore, a user can add and/or remove power tool devices from the inventory through the mobile electronic device 108 and/or through the external device 116. Stated another way, the mobile electronic device 108 and the external device 116 provide user interfaces into an inventory database 145 primarily stored on the server 112.
The external device 116 launches the inventory and reporting application in response to a user input (e.g., selecting an icon, opening a webpage, etc.). When the external device 116 launches the inventory and reporting application, the external device 116 requests a user to input a username (e.g., e-mail address) and a password, thereby identifying him/herself to the external device 116, to the inventory and reporting application, and to the server 112. Once the user has inputted his/her account information, the external wireless communication controller 128 communicates with the remote server 112 to ensure that the user is an authorized user and to obtain information regarding the power tool devices 104 that are specifically associated with the identified user.
As shown in
As shown in
As also shown in
The home screen 148 illustrates the list 152 of the power tool devices associated with the identified user, a search bar 156, a filters option 160, and an add item option 164. The search bar 156 allows a user to search for a particular power tool device by keywords (e.g., impact drill or 18V pack). The filters option 160 allows the user to restrict the display of the power tool devices 104 to only those power tool devices that meet certain criteria. In the illustrated embodiment, a filter can be applied according to a manufacturer, a category, and a location. In other embodiments, other filters can be used in addition or instead of the filters in the illustrated embodiment. In some embodiments, the user can select which filters are available. A user can select the add item option 164 to add a new power tool device 104 to the inventory associated with the identified user.
As shown in
In some embodiments, some of the information received by the inventory and reporting application is required to save a new power tool device (e.g., a device number associated with the power tool device), and some of the information is optional (e.g., a customized name for the power tool device). In other words, while a minimum set of information is required to add a new power tool device 104 to the inventory, some of the information is optional and the power tool device can be added with or without the additional information. For example, a user may be required to enter a tool number and a tool name, but may not be required to enter a location and/or purchasing price. In such embodiments, the external unit 116 may receive the required information from the manufacturer server and allow the user to add in any optional information. Such embodiments allow a user to search, select the desired power tool device, and save without further data entry, which makes the process of adding power tool devices 104 to the inventory faster.
If, on the other hand, the user wishes to add a power tool device from a manufacturer that is not connected to the external device 116 (e.g., power tool device 104d), the inventory and control application displays a screen with empty text boxes to be filled by the user (step 194). The user then inputs the information for the power tool device (step 198). Notably, in such embodiments, the external device 116 does not populate the text boxes with information received from the remote server 112. Rather, the text boxes remain blank for the user to fill them in, as shown in
When the inventory has been altered (e.g., due to an addition of a power tool device and/or due to loss of a power tool device), the inventory and control application on the external device 116 communicates with the server 112 to update the stored information regarding the inventory. The remote server 112 stores the new information for the inventory associated with the user. The next time the user accesses the inventory and reporting application on the external device 116 or on the mobile electronic device 108, the inventory and reporting application would display the most recent inventory information for the user.
Referring back to
A user can alternatively or additionally access the inventory and reporting application via the mobile electronic device 108. For example, a user can add power tool devices to his/her inventory through the mobile electronic device 108. As shown in
The memory 216 of the mobile electronic device 108 also stores core application software 220.
Once the mobile electronic device 108 receives the list of power tool devices 104 associated with the user from the server 112, the mobile electronic device 108 displays the list of associated power tool devices on the touch display 212 (step 232). Similar to the list 152 shown in
When the mobile electronic device 108 receives information from the server 112 regarding the power tool devices 104 associated with the identified user, the mobile electronic device 108 also determines the state of the power tool devices 104. The mobile electronic device 108 determines the state or status of the power tool devices 104 based on communication with the power tool devices 104 themselves. The power tool devices 104 can be in a connectable state, an advertisement state, an out of range state, or an unconnectable state. When the power tool device 104 is in the connectable state, the power tool device 104 has sufficient energy (e.g., because the power tool device 104 is connected to a battery pack) to begin data exchange between the power tool device 104 and the mobile electronic device 108. In the connectable state, the power tool device 104 communicates a tool number, a customized name, and an indication that sufficient power for data exchange is available. The inventory and reporting application indicates that the power tool device is in the connectable state by showing a communication symbol 238 next to the power tool device 104. The power tool device 104 is in an advertisement state when the power tool device is not connected to a main power source (e.g., a battery pack) that may provide sufficient energy to sustain data exchange. Rather, in the advertisement state, the power tool device 104 receives power only through the back-up power supply 110. When the power tool device 104 is in the advertisement state, the power tool device 104 does not have sufficient energy to sustain data exchange, but the power tool device 104 communicates the customized name, a tool device number, and/or a state of charge of a secondary battery. The inventory and reporting application indicates that the power tool device is in the advertisement state by graying out or not showing the communication symbol 238 and/or by graying out the power tool device.
When the power tool device 104 is out of range, the inventory and reporting application also show the power tool device 104 grayed out. Finally, when the power tool device 104 is in the unconnectable state, the power tool device 104 is not configured to communicate with the mobile electronic device 108. For example, power tool 104d is not configured to communicate with the mobile electronic device and would therefore be in the unconnectable state. The inventory and reporting application also show unconnectable power tool devices 104 in a grayed out form. In other embodiments, different ways of indicating the status of the power tool devices 104 are implemented. In particular, in some embodiments, each state of the power tool device is illustrated (e.g., using different colors for the symbol 238, showing different symbols, and/or including an information column that explicitly indicates the state of the power tool device 104) differently than another state of the power tool device 104 to readily be able to identify the state of the power tool device 104.
The inventory screen 236 includes a search box 240, a menu option 244, and an add item option 248. The search box 240 allows a user to search within his/her inventory for a particular tool using keywords. The keywords may be associated with a customized name of the power tool, a description of the power tool, a location, a model or serial number, etc. The menu option 244 may allow the user to select how to display the list of associated power tool devices 104. For example, the menu option 244 may allow the user to display the power tool devices according to the location, the manufacturer, etc. As shown in
The user may select the add item option 248 to add a power tool device to his/her inventory through the mobile inventory and reporting application.
When the user wishes to add a nearby power tool device 104, the user selects the nearby device option 264. In response to receiving the nearby device option 264, the mobile inventory and reporting application broadcasts a ping signal from the mobile electronic device 108 to the power tool devices within the communication range of the mobile electronic device 108 (step 270). Only those power tool devices 104 that are within the communication range of the mobile electronic device 108 and that are configured to communicate wirelessly with the mobile electronic device 108 (e.g., the communicating power tool devices 104a-c) respond to the ping signal from the mobile electronic device 108. The inventory and reporting application then receives responses from the communicating power tool devices 104a-c within the communication range (step 274). The responses from the communicating power tool devices 104a-c include identification information for each power tool device. The identification information includes, for example, a customized name associated with the power tool device, a model number, a unique identifier, a tool number, etc. In some embodiments, the power tool devices 104 periodically broadcast the identification information for the power tool device 104 without requiring a ping signal from the mobile electronic device 108 to be received. In such embodiments, step 270 in which the mobile electronic device 108 sends a ping signal to the power tool devices 104 nearby is bypassed.
The inventory and reporting application then compares the received responses to the power tool devices already in the inventory (step 278). If a received response corresponds to a power tool device 104 that is already part of the inventory, the inventory and reporting application does not display that power tool device 104 to the user and continues to check the rest of the responses (step 282). If, on the other hand, the received response corresponds to a power tool device 104 that is not part of the inventory, the inventory and reporting application displays the power tool device 104 to the user (step 286). Thereby, the inventory and reporting application only displays those power tool devices 104 that are nearby and that are not already part of the inventory for the user.
Enabling the user to add power tool devices that are nearby saves a significant amount of time because the user no longer has to manually search for a particular power tool device, input necessary information, etc. Instead, the mobile inventory and reporting application automatically determines which of the nearby power tool devices 104 are not yet part of the user's inventory and requests information for the inventory from the power tool devices 104 directly.
Referring back to
The user can then add more information regarding the selected power tool device 104, if the user, for example, wishes to input more information or additional notes (step 322). When the information has been gathered regarding the new power tool device 104, the user selects a “save” option, and the inventory and reporting application saves the information and adds the new power tool device to the user's inventory (step 326). The inventory and reporting application then displays the new power tool device 104 as part of the list 152 of power tool devices in the user's inventory (step 330).
Referring back to
Once the power tool devices 104 have been added to the user's inventory, the power tool devices are displayed as part of the user's inventory. Referring back to
In response to selecting the arrow 366, the inventory and reporting application displays a product information screen 370 for the selected power tool device as shown in
In the illustrated embodiment, the selected power tool device (e.g., Bob's Tool) does not include information regarding the category 378 of power tool device and the location 362 of the power tool device. The user then selects the edit selector 386 to add in a category and a location for the power tool device (e.g., Bob's Tool). In response to detecting that the user clicked on the edit selector 386, the mobile inventory and reporting application displays an editable version of the product information screen 370. As shown in
Executing the inventory and reporting application on the mobile electronic device 108 also provides other features such as tool device attendance, inventory sectioning, and location tracking. Tool device attendance is a feature that allows users to determine whether the tool devices 104 in his/her inventory are within a communication range of the mobile electronic device 108, thus allowing a user to quickly identify whether power tool devices 104 are missing and if so, which ones.
The mobile inventory and reporting application then generates a list of the power tool devices 104 that sent a response signal (or those that broadcasted the power tool device identification information) to the mobile electronic device 108 (step 406). The mobile inventory and reporting application compares the list of power tool devices 104 that sent a response signal to the power tool devices 104 that are part of the user's inventory (step 410). Based on the comparison of the two lists, the mobile inventory and reporting application determines which power tool devices 104 from the user's inventory are not within a communication range of the mobile electronic device 108 (step 414). The mobile inventory and reporting application displays a list of the “missing” power tool devices to the user (step 418). Since the user's inventory may also include power tool devices that do not communicate wirelessly with the mobile electronic device 108 (e.g., power tool 104d), the inventory and reporting application also displays a list of the power tool devices 104 that are not configured to communicate with the mobile electronic device 108 (step 422). The inventory and control application can also display, in response to a user selection, a separate list of these power tool devices 104 that were found.
The user can determine, based on the list provided by the inventory and reporting application, how many power tool devices 14 are missing and which power tool devices 104 are missing. The user can also delete these power tool devices 104 from the inventory, or edit the information associated with these power tool devices 104. The tool attendance feature can be implemented, for example, at the beginning of the work day to establish which tools are present at the particular worksite, at the end of the work day to ensure that the tools which were present at the beginning of the day are returned at the end of the day, and when transporting tools from one jobsite to another to ensure that the power tool devices 104 were delivered to the appropriate jobsite. The user can also save an attendance log including a time, date, and location stamp. The attendance log includes a listing of the power tool devices 104 that were nearby (e.g., found), and a separate listing the power tool devices 104 that were in the user's inventory, but were not nearby (e.g., missing).
Running the inventory and reporting application on the mobile electronic device 108 also enables inventory sectioning. While a large entity (e.g., a contracting company) may have too many power tool devices for a mobile inventory and reporting application to conveniently track, an administrator can divide and assign particular power tool devices 104 to particular users (e.g., operators, foreman, crib manager, etc.). The administrator (e.g., a buyer) can run the inventory and reporting application on the external device 116 displaying the power tool devices 104 owned by the large entity. However, to accurately and efficiently track the power tool devices 104, the administrator may separate the power tool devices 104 into subsets, as illustrated in
Launching the inventory and reporting application on the mobile electronic device 108 also allows for location tracking of the power tool devices 104. As discussed above, each of the power tool devices 104 is associated with a location. The location is an assigned location (e.g., where the power tool device is supposed to be). If a transfer of power tool devices 104 is desired, a user can use the inventory and reporting application to change the assigned location to track where the power tool device 104 is being transported. The inventory and reporting application can also save, display, and output information regarding a particular power tool device's location history. In other words, a user may determine where the power tool device has been before and may be able to better determine a probable location for the power tool device if, for example, the power tool device 104 is misplaced.
For example, the location tracking would also enable a user at the external device 116 to determine that power tool devices 104 are to be transported from jobsite A to jobsite B. The users at both jobsite A and jobsite B may be notified via communication from the remote server 112 that at least some of the power tool devices 104 from jobsite A are to be transported to jobsite B. A user at jobsite A may then arrange for the transportation of the power tool devices 104 according to the received notification.
In the illustrated embodiment, when a user launches the mobile inventory and reporting application at the mobile electronic device 108, the inventory and reporting application also indicates the status of each of the power tool devices 104 to the user. The power tool devices 104 may be in an advertisement state in which the power tool device 104 provides minimal identification information, but may not engage in further electronic data transfer between the power tool device 104 and the mobile electronic device 108. The power tool devices 104 may alternatively be in the connectable state in which the power tool device 104 provides identification information and may readily engage in electronic data transfer between the power tool device 104 and the mobile electronic device 108. Additionally, the mobile inventory and reporting application may indicate when a power tool is in use.
The inventory and reporting application also allows a user to analyze the operation of a particular power tool device and generate technical reports regarding the operation of the power tool device 104 or a group of power tool devices 104. In the illustrated embodiment, the operation of a hydraulic crimper is analyzed and the user receives information regarding the performance of the hydraulic crimper on both the mobile electronic device 108 and the external device 116.
As discussed above, the mobile electronic device 108 can wirelessly communicate with communicating power tool devices 104a-c. As also discussed above, the mobile inventory and reporting application can display a list of nearby power tool devices. A user can select one of these devices, and the mobile inventory and reporting application displays a power tool device home screen 500 (
As shown in
The crimper 510 also includes a wireless communication module 109 and a back-up power supply 110 as discussed with respect to
The home screen 500 of the crimper 510, or any other power tool device, also includes a sync tool data selector 580 and a view tool details selector 585. Selecting the sync tool data selector 580 initiates electronic data transfer from the crimper 510 to the mobile electronic device 108. The electronic data includes pressure and other sensor data associated with each operation the crimper 510 has performed since the last sync. Selecting the view tool details selector 585 allows a user to change tool information as discussed above with respect to the inventory feature. In some embodiments, the view tool details selector 585 also enables the user to configure modes for the crimper 510, change operating parameters, etc.
When the crimper 510 sends the operational data to the mobile electronic device 108, the mobile electronic device 108 compares the pressure data to a predetermined full pressure range (e.g., a high pressure threshold and a low pressure threshold). For each operation completed by the crimper 510, the mobile electronic device 108 determines whether the final pressure reached by the crimper 510 is within the predetermined full pressure range. If the final pressure is within the predetermined full pressure range, the crimper 510 is considered to have completed a full pressure cycle. If, however, the final pressure is outside (e.g., below or above) the predetermined full pressure range, the crimper 510 is considered to not have reached full pressure. This determination made by the mobile electronic device 108 generates the counts shown in the home screen 500 of the crimper 510. Specifically, by comparing the received final pressure information to the predetermined full pressure range, the mobile electronic device 108 is able to determine how many cycles the crimper 510 has completed, and how many of the completed cycles were completed to full pressure 510, as shown in
The mobile electronic device 108 communicates with the remote server 112 to forward the final pressure data points, the total number of cycles completed by the crimper 510, and the total number of full pressure cycles completed by the crimper 510. The remote server 112 can store the performance analysis for the crimper 510. When the inventory and reporting application is launched on the external device 116, the external device 116 communicates with the remote server 112 to receive updated information regarding the power tool devices 104.
The inventory and reporting application includes a reporting option 600 when launched on the external device 116. Selecting the reporting option 600 allows a user to have access to performance data for different power tool devices and generate meaningful reports on the performance of specific power tool devices or groups of power tool devices.
The inventory and reporting application generates common performance metrics applicable to all the displayed power tool devices 104 and displays the common performance metrics on the quick reporting area (step 618). The quick reporting area 612 indicates select metrics related to the operation of the power tool devices listed. In
In the illustrated embodiment, the power tool device list 616 includes only crimpers. The crimpers shown in the power tool device list 616 provide the power tool usage data to generate the common performance metrics shown in the quick reporting area 612. Once the user has specified the type of power tool devices to be used, the user also specifies the date range for the report. The date range field 608 is used to specify a particular time period for which power tool device performance is analyzed. In one example, the performance report is run four times per year. In other embodiments, the performance report may be run more or less frequently. As shown in
The list 616 of power tool devices, specifically crimpers 510, provides information to the user regarding the power tool devices. The information shown to the user is received by the external device 116 from the server 112. As shown in
As shown in
From the list 616 of the power tool devices, the user can also select one or more power tool devices (e.g., crimper 510) to analyze their performance by selecting specific checkboxes 646 shown in
After the user sufficiently verified the information shown on the information screen 650, the inventory and reporting application displays an alert screen 680 to the user (step 682). The alert screen 680, as shown in
After addressing the alerts 684, the inventory and reporting application generates a report that analyzes the performance of one or more specific power tool devices (step 686). As shown in
The report also includes a graphical display 690 illustrating specific data points of the performance data. In the illustrated embodiments, the graphical display 609 includes information regarding the final pressure reached by the crimper 510 and the full pressure range. As shown in
Although the reports generated by the inventory and reporting application were only described in relation to the crimper, similar methods can be followed for other and different electric power tool devices. Additionally, although the generated report was illustrated in a particular set-up, other arrangements of information may be implemented based on user preferences and/or specific power tool devices.
The mobile electronic device 108 receives a selection to detect nearby tools (step 708). As described above, the mobile electronic device 108 may receive the selection when a user selects a “tool attendance” selector on the inventory screen 236 of
The mobile electronic device 108 determines that a subset of the first plurality of power tools is not nearby (i.e., missing) based on the identification signals received (step 716). As described above, the mobile electronic device 108 compares the list of the first plurality of electronic device to the second plurality of electronic devices. The mobile electronic device 108 determines which of the first plurality of electronic devices are or not found nearby based on the identification signals. The subset of the first plurality of electronic devices may include only one power tool 104 or multiple power tools 104. That is, the mobile electronic device 108 may determine that one or more of the first plurality of power tools is or not found nearby by determining that a signal was not received from the one or more power tools 104 making up the subset within a predetermined time period. Thus, the absence of a signal from a particular power tool 104 indicates to the mobile electronic device 108 that the particular tool is not nearby. The mobile electronic device 108 generates an indication that the subset of the first plurality of power tools is not nearby (i.e., missing) (step 720). As described above, the mobile electronic device 108 may display the subset of the first plurality of power tools on the touch display 212.
In some embodiments, the inventory and reporting application receives, from one or more mobile electronic devices 108, the voltage levels of the back-up power supplies 110 of a plurality of the power tools 104. As described above, the one or more mobile electronic devices 108 receive the voltage levels of the back-up power supplies 110 wirelessly from the respective power tools 104 via respective wireless communication controllers 109. The inventory and reporting application, in turn, generates a list of the power tools 104 and the voltage levels of the respective back-up power supplies 110. Additionally, the inventory and reporting application determines whether each voltage level is below a first low battery threshold and whether each voltage level is below a second low battery threshold. The second low battery threshold is a lower level than the first low battery threshold and is indicative of a back-up power supply being nearer to depletion and in need of replacement. The inventory and reporting application then generates an indication (e.g., warning icon 645) for each power tool having a back-up power supply 110 with a voltage level below the first or second low battery threshold. For example, with reference to
The mobile electronic device 108 receives identification signals from a plurality of power tool devices 104 within communication range of the mobile electronic device 108 (at step 732). As described above, the power tools 104a-c broadcast identification information for the power tool device 104. The mobile electronic device 108 detects which power tool devices 104 are nearby based on the broadcast signals from the power tool devices 104. The power tools devices 104 may broadcast the signals periodically (unprompted by an external device) or may broadcast in response to a ping from the mobile electronic device 108.
The mobile electronic device 108 displays identification information of the plurality of power tool devices 104 (at step 736). For example, the mobile electronic device 108 displays the identification information on a touch display 212 of the mobile electronic device 108. The mobile electronic device 108 receives a selection of a power tool device 104 from the plurality of power tool devices 104 (at step 740). As described above, the mobile electronic device 108 receives the selection of the power tool device 104 when the user selects the power tool device 104 on the touch display 212 of the mobile electronic device 108.
The mobile electronic device 108 adds the power tool device 104 to the inventory list (at step 744). As described above, the mobile electronic device 108 and the inventory and reporting application save the information of the power tool device 104 to the inventory list. The inventory list may be stored on the remote server 112.
In some embodiments, another process is provided for adding a new power tool device using the mobile electronic device 108 to an inventory of a user. With reference to
The inventory and reporting application then compares the received responses to the power tool devices already in the inventory of the user. If a received response corresponds to a power tool device 104 that is already part of the inventory, the inventory and reporting application does not display that power tool device 104 to the user and continues to check the rest of the responses (step 282). If, on the other hand, the received response corresponds to a power tool device 104 that is not part of the inventory, the inventory and reporting application displays the power tool device 104 to the user (step 286). Thereby, the inventory and reporting application only displays those power tool devices 104 that are nearby and that are not already part of the inventory for the user. See, for example,
The mobile electronic device 108 displays identification information of the plurality of power tool devices 104 (at step 756). As described above, the mobile electronic device 108 may display the identification information on a touch display 212 of the mobile electronic device 108. The mobile electronic device 108 receives a selection of a power tool device 104 to be analyzed from the plurality of power tool devices 104 (at step 760). As described above, the mobile electronic device 108 may receive the selection of the power tool device 104 when the user selects the power tool device 104 on the touch display 212 of the mobile electronic device 108.
The mobile electronic device 108 receives metrics information regarding the power tool device 104 in response to the selection of the power tool device 104 to be analyzed (at step 764). As described above, the mobile electronic device 108 receives metrics information of the power tool device 104 via the short-range transceiver, for example over a Bluetooth® connection. The power tool device 104 may transmit the metrics information when it receives a request from the mobile electronic device 108 in response to the selection or a further user input (e.g., by selecting the sync tool data selector 580 (
The mobile electronic device 108 displays the metrics information for the power tool device (at step 768). As described above, the mobile electronic device 108 may display the metrics information on a touch display 212 of the mobile electronic device 108 (see, e.g.,
Throughout the above description, reference is made to the inventory and reporting application or other software as taking action (e.g., receiving, generating, displaying, and the like). Such actions may be performed by the device on which the application or software is being executed (e.g., the mobile device 108 or the external device 116) in response to or based on the execution of the application or software on that device.
Thus, the invention provides, among other things, a system that allows a user to control, manage, and maintain a large number of power tool devices. Various features and advantages of the invention are set forth in the following claims.
This application is a continuation of U.S. patent application Ser. No. 15/183,445, filed Jun. 15, 2016, now U.S. Pat. No. 10,339,496, which claims priority to U.S. Provisional Patent Application No. 62/175,957, filed on Jun. 15, 2015, the entire contents of all of which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3597742 | Phillips et al. | Aug 1971 | A |
3882305 | Johnstone | May 1975 | A |
4545106 | Juengel | Oct 1985 | A |
5528248 | Steiner et al. | Jun 1996 | A |
5563607 | Loomis et al. | Oct 1996 | A |
5592396 | Tambini et al. | Jan 1997 | A |
5604506 | Rodal | Feb 1997 | A |
5629693 | Janky | May 1997 | A |
5719587 | Rodal | Feb 1998 | A |
5760742 | Branch et al. | Jun 1998 | A |
5903462 | Wagner et al. | May 1999 | A |
6031488 | Hua et al. | Feb 2000 | A |
6046687 | Janky | Apr 2000 | A |
6055484 | Lysaght | Apr 2000 | A |
6097337 | Bisio | Aug 2000 | A |
6123241 | Walter et al. | Sep 2000 | A |
6157313 | Emmermann | Dec 2000 | A |
6161629 | Hohmann et al. | Dec 2000 | A |
6184801 | Janky | Feb 2001 | B1 |
6225890 | Murphy | May 2001 | B1 |
6232874 | Murphy | May 2001 | B1 |
6279668 | Mercer | Aug 2001 | B1 |
6343276 | Barnett | Jan 2002 | B1 |
6349266 | Lysaght et al. | Feb 2002 | B1 |
6390205 | Wallgren et al. | May 2002 | B2 |
6405598 | Bareggi | Jun 2002 | B1 |
6430416 | Loomis | Aug 2002 | B1 |
6469615 | Kady et al. | Oct 2002 | B1 |
6520270 | Wissmach et al. | Feb 2003 | B2 |
6522949 | Ikeda et al. | Feb 2003 | B1 |
6536880 | Takagi | Mar 2003 | B2 |
6547014 | McCallops et al. | Apr 2003 | B2 |
6611755 | Coffee et al. | Aug 2003 | B1 |
6668212 | Colangelo, II et al. | Dec 2003 | B2 |
6675196 | Kronz | Jan 2004 | B1 |
6677938 | Maynard | Jan 2004 | B1 |
6768994 | Howard et al. | Jan 2004 | B1 |
6732077 | Gilbert et al. | May 2004 | B1 |
6784801 | Watanabe et al. | Aug 2004 | B2 |
6801853 | Workman | Oct 2004 | B2 |
6848516 | Giardino | Feb 2005 | B2 |
6853909 | Scherzinger | Feb 2005 | B2 |
6872121 | Wiener et al. | Mar 2005 | B2 |
6892131 | Coffee et al. | May 2005 | B2 |
6913087 | Brotto et al. | Jul 2005 | B1 |
6923285 | Rossow et al. | Aug 2005 | B1 |
6934631 | Dentinger et al. | Aug 2005 | B2 |
6938689 | Farrant et al. | Sep 2005 | B2 |
6954048 | Cho | Oct 2005 | B2 |
6980812 | Sandhu et al. | Dec 2005 | B1 |
6981311 | Seith et al. | Jan 2006 | B2 |
7020555 | Janky et al. | Mar 2006 | B1 |
7034711 | Sakatani et al. | Apr 2006 | B2 |
7035710 | Balling | Apr 2006 | B2 |
7036703 | Grazioli et al. | May 2006 | B2 |
7043364 | Scherzinger | May 2006 | B2 |
7050907 | Janky et al. | May 2006 | B1 |
7064502 | Garcia et al. | Jun 2006 | B2 |
7086483 | Arimura et al. | Aug 2006 | B2 |
7089113 | Janky et al. | Aug 2006 | B1 |
7102303 | Brotto et al. | Sep 2006 | B2 |
7117169 | Zara et al. | Oct 2006 | B2 |
7123149 | Nowak et al. | Oct 2006 | B2 |
7137541 | Baskar et al. | Nov 2006 | B2 |
7158885 | Janky et al. | Jan 2007 | B1 |
7211972 | Garcia et al. | May 2007 | B2 |
7218227 | Davis et al. | May 2007 | B2 |
7243440 | DeKeyser | Jul 2007 | B2 |
7263441 | Janky et al. | Aug 2007 | B1 |
7283090 | Dentinger et al. | Oct 2007 | B2 |
7298240 | Lamar | Nov 2007 | B2 |
7313476 | Nichols et al. | Dec 2007 | B2 |
7319395 | Puzio et al. | Jan 2008 | B2 |
7328086 | Perry et al. | Feb 2008 | B2 |
7328757 | Davies | Feb 2008 | B2 |
7330129 | Crowell et al. | Feb 2008 | B2 |
7336181 | Nowak et al. | Feb 2008 | B2 |
7343764 | Solfronk | Mar 2008 | B2 |
7346406 | Brotto et al. | Mar 2008 | B2 |
7346422 | Tsuchiya et al. | Mar 2008 | B2 |
7348921 | Yu | Mar 2008 | B2 |
7359762 | Etter et al. | Apr 2008 | B2 |
7365681 | Yu | Apr 2008 | B2 |
7376599 | Gerhardt | May 2008 | B1 |
7382272 | Feight | Jun 2008 | B2 |
7383882 | Lerche et al. | Jun 2008 | B2 |
7398153 | Workman et al. | Jul 2008 | B2 |
7415355 | Janky et al. | Aug 2008 | B2 |
7431682 | Zeiler et al. | Oct 2008 | B2 |
7437204 | Lev-Ami et al. | Oct 2008 | B2 |
7453355 | Bergstrom et al. | Nov 2008 | B2 |
7464769 | Nakazawa et al. | Dec 2008 | B2 |
7466263 | Yu | Dec 2008 | B1 |
7468650 | Childress et al. | Dec 2008 | B2 |
7480568 | Dentinger et al. | Jan 2009 | B2 |
7489993 | Coffee et al. | Feb 2009 | B2 |
7540334 | Gass et al. | Jun 2009 | B2 |
7580794 | Janky et al. | Aug 2009 | B2 |
7613590 | Brown | Nov 2009 | B2 |
7623248 | Laflamme | Nov 2009 | B2 |
7627427 | Nichols et al. | Dec 2009 | B2 |
7627503 | Champagne et al. | Dec 2009 | B1 |
RE41185 | Gilmore et al. | Mar 2010 | E |
7679552 | Dentinger et al. | Mar 2010 | B2 |
7690569 | Swanson et al. | Apr 2010 | B2 |
7739138 | Chauhan et al. | Jun 2010 | B2 |
7742874 | Mayfield et al. | Jun 2010 | B1 |
7750811 | Puzio et al. | Jul 2010 | B2 |
7755482 | Hubbard | Jul 2010 | B2 |
7772850 | Bertness | Aug 2010 | B2 |
7773945 | Reynolds | Aug 2010 | B2 |
7783423 | Verma et al. | Aug 2010 | B2 |
7784104 | Innami et al. | Aug 2010 | B2 |
7787981 | Austin et al. | Aug 2010 | B2 |
7809495 | Leufen | Oct 2010 | B2 |
7817062 | Li et al. | Oct 2010 | B1 |
7830993 | Riley et al. | Nov 2010 | B2 |
7850071 | Sakamoto et al. | Dec 2010 | B2 |
7868591 | Phillips et al. | Jan 2011 | B2 |
7898391 | Maguire et al. | Mar 2011 | B2 |
7898403 | Ritter et al. | Mar 2011 | B2 |
7900524 | Calloway et al. | Mar 2011 | B2 |
7911379 | Cameron | Mar 2011 | B2 |
7917654 | Toivonen | Mar 2011 | B2 |
7928845 | LaRosa | Apr 2011 | B1 |
7931096 | Saha | Apr 2011 | B2 |
7941330 | Buentello et al. | May 2011 | B1 |
7942084 | Wilson, Jr. et al. | May 2011 | B2 |
7942211 | Scrimshaw et al. | May 2011 | B2 |
7953965 | Qin et al. | May 2011 | B2 |
7961078 | Reynolds et al. | Jun 2011 | B1 |
7982624 | Richter et al. | Jul 2011 | B2 |
7999658 | Reynolds et al. | Aug 2011 | B1 |
8004397 | Forrest et al. | Aug 2011 | B2 |
8004664 | Etter et al. | Aug 2011 | B2 |
8005647 | Armstrong et al. | Aug 2011 | B2 |
8020768 | Ramos-Elizondo | Sep 2011 | B2 |
8022814 | Yogeeswaran et al. | Sep 2011 | B2 |
8032152 | Manson et al. | Oct 2011 | B2 |
8041591 | Kawai et al. | Oct 2011 | B2 |
8049636 | Buckingham et al. | Nov 2011 | B2 |
8068848 | Manson et al. | Nov 2011 | B2 |
8068849 | Manson et al. | Nov 2011 | B2 |
8081063 | Maguire | Dec 2011 | B2 |
8081987 | Manson et al. | Dec 2011 | B2 |
8081988 | Manson et al. | Dec 2011 | B2 |
8081989 | Manson et al. | Dec 2011 | B2 |
8095149 | Manson et al. | Jan 2012 | B2 |
8103438 | Petrie et al. | Jan 2012 | B2 |
8125529 | Skoskiewicz et al. | Feb 2012 | B2 |
8144000 | Darby, Jr. et al. | Mar 2012 | B2 |
8159345 | Stevens | Apr 2012 | B2 |
8161613 | Schuele et al. | Apr 2012 | B2 |
8171828 | Duvan et al. | May 2012 | B2 |
8210275 | Suzuki et al. | Jul 2012 | B2 |
8224518 | Cameron | Jul 2012 | B2 |
8225319 | Laithwaite et al. | Jul 2012 | B2 |
8239125 | Petrie et al. | Aug 2012 | B2 |
8255358 | Ballew et al. | Aug 2012 | B2 |
8260322 | Allen et al. | Sep 2012 | B2 |
8260452 | Austin et al. | Sep 2012 | B2 |
8264374 | Obatake et al. | Sep 2012 | B2 |
8279112 | Carrick | Oct 2012 | B2 |
8280784 | Hurtis et al. | Oct 2012 | B2 |
8281871 | Cutler et al. | Oct 2012 | B2 |
8286723 | Puzio et al. | Oct 2012 | B2 |
8294424 | Bucur | Oct 2012 | B2 |
8306836 | Nichols et al. | Nov 2012 | B2 |
8310206 | Bucur | Nov 2012 | B2 |
8319950 | Snyder | Nov 2012 | B2 |
8330426 | Suzuki et al. | Dec 2012 | B2 |
8330580 | Reynolds et al. | Dec 2012 | B2 |
8344879 | Harmon et al. | Jan 2013 | B2 |
8351982 | Rofougaran | Jan 2013 | B2 |
8374926 | Solomon | Feb 2013 | B2 |
8386283 | Hand | Feb 2013 | B2 |
8406697 | Arimura et al. | Mar 2013 | B2 |
8412179 | Gerold et al. | Apr 2013 | B2 |
8429034 | Cerbone | Apr 2013 | B2 |
8438955 | Wilson, Jr. et al. | May 2013 | B2 |
8446254 | Carrick et al. | May 2013 | B2 |
8482721 | Snyder | Jul 2013 | B2 |
8484370 | Coffee et al. | Jul 2013 | B1 |
8485049 | Yokoyama et al. | Jul 2013 | B2 |
8493243 | Ahmadi et al. | Jul 2013 | B2 |
8514058 | Cameron | Aug 2013 | B2 |
8576095 | Harmon et al. | Nov 2013 | B2 |
8589273 | Creeden et al. | Nov 2013 | B2 |
8600932 | Poling et al. | Dec 2013 | B2 |
8611250 | Chen et al. | Dec 2013 | B2 |
8618949 | Maynard et al. | Dec 2013 | B2 |
8638375 | Amor Molares et al. | Jan 2014 | B2 |
8639434 | Snoeck et al. | Jan 2014 | B2 |
8645176 | Walton et al. | Feb 2014 | B2 |
8657482 | Malackowski et al. | Feb 2014 | B2 |
8666936 | Wallace | Mar 2014 | B2 |
8668136 | Ahern et al. | Mar 2014 | B2 |
8682541 | Best et al. | Mar 2014 | B2 |
8725777 | Deking et al. | May 2014 | B2 |
8755161 | James | Jun 2014 | B2 |
8768609 | Maynard et al. | Jul 2014 | B2 |
8768667 | Lindores | Jul 2014 | B2 |
8776644 | Harper et al. | Jul 2014 | B2 |
8788496 | Darby, Jr. et al. | Jul 2014 | B2 |
8791806 | Granruth | Jul 2014 | B2 |
8818617 | Miller et al. | Aug 2014 | B2 |
8855937 | Lindores | Oct 2014 | B2 |
8915430 | Shah et al. | Dec 2014 | B2 |
8919456 | Ng et al. | Dec 2014 | B2 |
8928463 | Landau et al. | Jan 2015 | B2 |
8947225 | Best et al. | Feb 2015 | B2 |
8954222 | Costantino | Feb 2015 | B2 |
8954227 | Bertosa et al. | Feb 2015 | B2 |
8965841 | Wallace | Feb 2015 | B2 |
8970377 | Heine et al. | Mar 2015 | B2 |
8981680 | Suda et al. | Mar 2015 | B2 |
8996237 | Bertosa et al. | Mar 2015 | B2 |
9002572 | Lipscomb et al. | Apr 2015 | B2 |
9031585 | Kahle et al. | May 2015 | B2 |
9033219 | Schoner et al. | May 2015 | B2 |
9041561 | Wallace et al. | May 2015 | B2 |
9043402 | Fosburgh et al. | May 2015 | B2 |
9061392 | Forgues et al. | Jun 2015 | B2 |
9073134 | Koeder et al. | Jul 2015 | B2 |
9092753 | Fanelli | Jul 2015 | B1 |
9094793 | Kusakari et al. | Jul 2015 | B2 |
9111234 | Wallace et al. | Aug 2015 | B2 |
9126317 | Lawton et al. | Sep 2015 | B2 |
9129248 | Reynolds et al. | Sep 2015 | B2 |
9177488 | Chontos et al. | Nov 2015 | B2 |
9194917 | Brochhaus | Nov 2015 | B2 |
9216505 | Rejman et al. | Dec 2015 | B2 |
9232614 | Hiroi | Jan 2016 | B2 |
9233457 | Wanek et al. | Jan 2016 | B2 |
9256988 | Wenger et al. | Feb 2016 | B2 |
9257865 | Hiuggins et al. | Feb 2016 | B2 |
9281770 | Wood et al. | Mar 2016 | B2 |
9298803 | Wallace | Mar 2016 | B2 |
9355495 | Miller | May 2016 | B2 |
9386907 | Vazales et al. | Jul 2016 | B2 |
9392404 | Daoura et al. | Jul 2016 | B2 |
9443432 | Tambini et al. | Sep 2016 | B2 |
9466198 | Burch et al. | Oct 2016 | B2 |
9467862 | Zeiler et al. | Oct 2016 | B2 |
9615450 | Hwang et al. | Apr 2017 | B2 |
9641964 | Kulkarni et al. | May 2017 | B2 |
9747632 | Hicks | Aug 2017 | B2 |
9749780 | Huang | Aug 2017 | B2 |
9754238 | Lyon | Sep 2017 | B2 |
9756402 | Stampfl et al. | Sep 2017 | B2 |
9766608 | Wuertele | Sep 2017 | B2 |
9773268 | Bonner et al. | Sep 2017 | B2 |
9792655 | Griffin et al. | Oct 2017 | B2 |
9811962 | Phillips et al. | Nov 2017 | B2 |
9815166 | Goldstein et al. | Nov 2017 | B2 |
9819132 | Peloquin et al. | Nov 2017 | B2 |
9886680 | Johnson et al. | Feb 2018 | B2 |
9898705 | Kahle et al. | Feb 2018 | B2 |
9898884 | Arora et al. | Feb 2018 | B1 |
9909760 | Chen et al. | Mar 2018 | B2 |
9916560 | Vasantham | Mar 2018 | B2 |
9928055 | Douberley et al. | Mar 2018 | B1 |
9934545 | Kropp | Apr 2018 | B2 |
9990669 | Nuzzi | Jun 2018 | B2 |
10152688 | DeBusk et al. | Dec 2018 | B2 |
10192197 | Rogers | Jan 2019 | B2 |
10229568 | Man | Mar 2019 | B2 |
10339496 | Matson | Jul 2019 | B2 |
10354181 | Freienstein | Jul 2019 | B2 |
10395076 | Phillips | Aug 2019 | B2 |
10410169 | Vasantham | Sep 2019 | B2 |
10430755 | Aji | Oct 2019 | B2 |
10445688 | Kondragunta | Oct 2019 | B2 |
10474987 | Corona | Nov 2019 | B2 |
10580060 | Olschan | Mar 2020 | B2 |
10625909 | Aman | Apr 2020 | B2 |
10647509 | Lyon | May 2020 | B2 |
10650654 | Batra | May 2020 | B2 |
20020128913 | Ower | Sep 2002 | A1 |
20030121677 | Kady et al. | Mar 2003 | A1 |
20030088442 | Michael | May 2003 | A1 |
20040182587 | May et al. | Sep 2004 | A1 |
20050035659 | Hahn et al. | Feb 2005 | A1 |
20050110639 | Puzio et al. | May 2005 | A1 |
20060009879 | Lynch et al. | Jan 2006 | A1 |
20060076385 | Etter et al. | Apr 2006 | A1 |
20060220955 | Hamilton | Oct 2006 | A1 |
20080001755 | Puzio et al. | Jan 2008 | A1 |
20080084324 | Wallace et al. | Apr 2008 | A1 |
20080084332 | Ritter et al. | Apr 2008 | A1 |
20080084333 | Forrest et al. | Apr 2008 | A1 |
20080084334 | Ballew | Apr 2008 | A1 |
20080086320 | Ballew et al. | Apr 2008 | A1 |
20080086321 | Walton | Apr 2008 | A1 |
20080086322 | Wallace | Apr 2008 | A1 |
20080086323 | Petrie et al. | Apr 2008 | A1 |
20080086349 | Petrie et al. | Apr 2008 | A1 |
20080086391 | Maynard et al. | Apr 2008 | A1 |
20080086427 | Wallace | Apr 2008 | A1 |
20080086428 | Wallace | Apr 2008 | A1 |
20080086497 | Wallace et al. | Apr 2008 | A1 |
20080086508 | Ballew | Apr 2008 | A1 |
20080086509 | Wallace | Apr 2008 | A1 |
20080086685 | Janky et al. | Apr 2008 | A1 |
20080181398 | Pappu | Jul 2008 | A1 |
20080252446 | Dammertz | Oct 2008 | A1 |
20090015585 | Klusza | Jan 2009 | A1 |
20090250364 | Gerold et al. | Oct 2009 | A1 |
20090251330 | Gerold et al. | Oct 2009 | A1 |
20090267769 | Stevens | Oct 2009 | A1 |
20100096151 | Östling | Apr 2010 | A1 |
20100154599 | Gareis | Jun 2010 | A1 |
20100176766 | Brandner et al. | Jul 2010 | A1 |
20100181964 | Kadous et al. | Jul 2010 | A1 |
20110056716 | Jönsson et al. | Mar 2011 | A1 |
20110067895 | Nobe et al. | Mar 2011 | A1 |
20110073343 | Sawano et al. | Mar 2011 | A1 |
20110162858 | Coste | Jul 2011 | A1 |
20110282631 | Poling et al. | Nov 2011 | A1 |
20110302051 | Arbatli | Dec 2011 | A1 |
20110309931 | Rose | Dec 2011 | A1 |
20120167721 | Fluhrer | Jul 2012 | A1 |
20120168189 | Eckert | Jul 2012 | A1 |
20120267134 | Matthias et al. | Oct 2012 | A1 |
20120292070 | Ito et al. | Nov 2012 | A1 |
20120325507 | Fluhrer et al. | Dec 2012 | A1 |
20130024245 | Nichols et al. | Jan 2013 | A1 |
20130035978 | Richardson et al. | Feb 2013 | A1 |
20130071815 | Hudson et al. | Mar 2013 | A1 |
20130087355 | Oomori et al. | Apr 2013 | A1 |
20130109375 | Zeiler et al. | May 2013 | A1 |
20130126202 | Oomori et al. | May 2013 | A1 |
20130133907 | Chen et al. | May 2013 | A1 |
20130133911 | Ishikawa et al. | May 2013 | A1 |
20130138465 | Kahle et al. | May 2013 | A1 |
20130138606 | Kahle et al. | May 2013 | A1 |
20130153250 | Eckert | Jun 2013 | A1 |
20130187587 | Knight et al. | Jul 2013 | A1 |
20130188058 | Nguyen et al. | Jul 2013 | A1 |
20130191417 | Petrie et al. | Jul 2013 | A1 |
20130204753 | Wallace | Aug 2013 | A1 |
20130255980 | Linehan et al. | Oct 2013 | A1 |
20130304545 | Ballew et al. | Nov 2013 | A1 |
20130327552 | Lovelass et al. | Dec 2013 | A1 |
20140006295 | Zeiler et al. | Jan 2014 | A1 |
20140015389 | Vatterott et al. | Jan 2014 | A1 |
20140052384 | Poling et al. | Feb 2014 | A1 |
20140070924 | Wenger et al. | Mar 2014 | A1 |
20140107853 | Ashinghurst et al. | Apr 2014 | A1 |
20140122143 | Fletcher et al. | May 2014 | A1 |
20140149416 | Wallace | May 2014 | A1 |
20140151079 | Furui et al. | Jun 2014 | A1 |
20140158389 | Ito et al. | Jun 2014 | A1 |
20140159662 | Furui et al. | Jun 2014 | A1 |
20140159919 | Furui et al. | Jun 2014 | A1 |
20140159920 | Furui et al. | Jun 2014 | A1 |
20140166324 | Puzio et al. | Jun 2014 | A1 |
20140184397 | Volpert | Jul 2014 | A1 |
20140266024 | Chinnadurai et al. | Sep 2014 | A1 |
20140284070 | Ng et al. | Sep 2014 | A1 |
20140292245 | Suzuki et al. | Oct 2014 | A1 |
20140304545 | Chen et al. | Oct 2014 | A1 |
20140316837 | Fosburgh et al. | Oct 2014 | A1 |
20140324194 | Larsson et al. | Oct 2014 | A1 |
20140331830 | King et al. | Nov 2014 | A1 |
20140334270 | Kusakawa | Nov 2014 | A1 |
20140336810 | Li et al. | Nov 2014 | A1 |
20140336955 | Li et al. | Nov 2014 | A1 |
20140350716 | Fly et al. | Nov 2014 | A1 |
20140365259 | Delplace et al. | Dec 2014 | A1 |
20140379136 | Schlegel et al. | Dec 2014 | A1 |
20150000944 | Dusselberg et al. | Jan 2015 | A1 |
20150002089 | Rejman et al. | Jan 2015 | A1 |
20150042247 | Kusakawa | Feb 2015 | A1 |
20150084745 | Hertz et al. | Mar 2015 | A1 |
20150097674 | Mondal et al. | Apr 2015 | A1 |
20150122524 | Papp | May 2015 | A1 |
20150127205 | Brochhaus | May 2015 | A1 |
20150135306 | Winkler et al. | May 2015 | A1 |
20150179036 | Heine et al. | Jun 2015 | A1 |
20150191096 | Becker et al. | Jul 2015 | A1 |
20150340921 | Suda et al. | Nov 2015 | A1 |
20150356858 | Daoura | Dec 2015 | A1 |
20160012389 | Xie | Jan 2016 | A1 |
20160088482 | Zeiler | Mar 2016 | A1 |
20160094934 | Yang et al. | Mar 2016 | A1 |
20170008159 | Boeck et al. | Jan 2017 | A1 |
20170201295 | Kusakawa | Jul 2017 | A1 |
20170353847 | Coulis et al. | Dec 2017 | A1 |
20180190103 | Daoura et al. | Jul 2018 | A1 |
Number | Date | Country |
---|---|---|
103056849 | Apr 2013 | CN |
10309703 | Sep 2004 | DE |
202006014606 | Jan 2007 | DE |
2147750 | Jan 2010 | EP |
2786338 | Oct 2014 | EP |
2884814 | Jun 2015 | EP |
2934030 | Oct 2015 | EP |
2000176850 | Jun 2000 | JP |
2004072563 | Mar 2004 | JP |
2006123080 | May 2006 | JP |
WO95021386 | Aug 1995 | WO |
WO2002030624 | Apr 2002 | WO |
WO2007090258 | Aug 2007 | WO |
WO2008063983 | May 2008 | WO |
2010114351 | Oct 2010 | WO |
WO2013063106 | May 2013 | WO |
WO2013063507 | May 2013 | WO |
Entry |
---|
European Patent Office Search Report for Application No. 17810845.2 dated Oct. 11, 2019, 10 pages. |
United States Patent Office Action for U.S. Appl. No. 16/522,856 dated Aug. 16, 2019 (14 pages). |
International Search Report and Written Opinion for Application No. PCT/2017/036128 dated Sep. 12, 2017. |
ASAP Systems “Barcloud Inventory Management & Asset Tracking Software” 2015, downloaded Jul. 13, 2015, (23 pages). |
Gigatrak, <http://www.gigatrak.com/>, 2010 (3 pages). |
International Search Report and Written Opinion for Application No. PCT/IB2016/000987 dated Dec. 9, 2016, 14 pages. |
ToolWatch, “ToolWatch Enterprise”, 2006 (8 pages). |
Trimble Alltrak, “Take Control of your Assets”, 2009, downloaded Jul. 13, 2015 (4 pages). |
European Patent Office Search Report for Application No. 16811092.2 dated Oct. 2, 2018, 8 pages. |
United States Patent Office Action for U.S. Appl. No. 16/164,960 dated Feb. 8, 2019, 14 pages. |
European Patent Office Examination Report for Application No. 16811092.2 dated Jan. 17, 2020 (5 pages). |
Number | Date | Country | |
---|---|---|---|
20190156278 A1 | May 2019 | US |
Number | Date | Country | |
---|---|---|---|
62175957 | Jun 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15183445 | Jun 2016 | US |
Child | 16261230 | US |