Managing construction assets

Abstract

A processing device receives, from a gateway, an identifier for a user account and identifiers for a plurality of construction assets detected by the gateway within a range of the gateway, where the user account is maintained by a backend server. The processing device determines that at least one construction asset in the plurality of construction assets is not associated with the user account based on the identifier for the user account and the identifiers for the plurality of construction assets. The processing device associates an identifier for the at least one construction asset with the user account based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the user account.

Description

SBD Ref. No. P-WO-TN-2024-1174Womble Ref. No. S122995 1140WOMANAGING CONSTRUCTION ASSETSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the benefit of priority to each of U.S. Provisional Patent Application No. 63 / 780,011, filed on March 28, 2025, entitled Systems and Methods for Construction Asset Auditing and Management, and U.S. Provisional Patent Application No.63 / 889,065, filed on September 26, 2025, entitled Managing Construction Assets.INCORPORATION BY REFERENCE

[0002] The disclosures of each of U.S. Provisional Patent Application No. 63 / 780,011, filed on March 28, 2025, entitled Systems and Methods for Construction Asset Auditing and Management, and U.S. Provisional Patent Application No. 63 / 889,065, filed on September 26, 2025, entitled Managing Construction Assets, are hereby incorporated by reference for all purposes as if set forth in their entireties.TECHNICAL FIELD

[0003] Aspects of the present disclosure relate to managing construction assets, and more particularly, to a site manager for asset and audit status management.BACKGROUND

[0004] At a jobsite (e.g., a construction site), many different types of tools (e.g., power tools), related accessories, and other construction supplies may be used at various times. For example, for a large scale construction project, hundreds or thousands of tools may be utilized. Tracking1WBD (US) 4911-1825-7051the locations and statuses of such tools, accessories, and other construction supplies may present challenges.SUMMARY

[0005] According to one aspect, the disclosure is generally directed to a method performed by a backend server for asset onboarding, comprising: receiving, from a gateway, an identifier for a user account and identifiers for a plurality of construction assets detected by the gateway within a range of the gateway, wherein the user account is maintained by the backend server; determining that at least one construction asset in the plurality of construction assets is not associated with the user account based on the identifier for the user account and the identifiers for the plurality of construction assets; and associating an identifier for the at least one construction asset with the user account based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the user account.

[0006] According to some example aspects, the method further comprises: determining that the at least one construction asset in the plurality of construction assets is not associated with additional user accounts maintained by the backend server based on the identifiers for the plurality of construction assets, wherein associating the identifier for the at least one construction asset with the user account is additionally based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the additional user accounts.

[0007] According to some example aspects, the method further comprises: receiving, from a user device, information pertaining to the at least one construction asset subsequent to associating the at least one construction asset with the user account; and associating the information pertaining to2WBD (US) 4911-1825-7051the at least one construction asset with the identifier for the at least one construction asset associated with the user account.

[0008] According to some example aspects, the method further comprises: receiving, from the user device and prior to receiving the information pertaining to the at least one construction asset, a request for a graphical user interface (GUI) for entering the information pertaining to the at least one construction asset; and causing the GUI for entering the information pertaining to the at least one construction asset to be presented on the user device.

[0009] According to some example aspects, the method further comprises: executing a search over a log of construction asset information based on the identifier for the at least one construction asset; identifying information pertaining to the at least one construction asset based on search results for the search; and associating the information pertaining to the at least one construction asset with the identifier for the at least one construction asset associated with the user account.

[0010] According to some example aspects, the identifier for the at least one construction asset comprises a medium access control (MAC) address.

[0011] According to some example aspects, the plurality of construction assets comprises at least one of tools or battery packs.

[0012] According to some example aspects, the gateway comprises a smartphone.

[0013] According to some example aspects, the method further comprises: transmitting, to a user device, an indication that the at least one construction asset has been associated with the user account.3WBD (US) 4911-1825-7051

[0014] According to another aspect, the disclosure is generally directed to a backend server, comprising: a processor; and memory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of the preceding aspects.

[0015] According to another aspect, the disclosure is generally directed to an apparatus comprising means for implementing a method as in any of the preceding aspects.

[0016] According to another aspect, the disclosure is generally directed to a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of the preceding aspects.

[0017] According to another aspect, the disclosure is generally directed to a computer program product for implementing a method as in any of the preceding aspects.

[0018] According to one aspect, the disclosure is generally directed to a method performed by a gateway for asset onboarding, comprising: performing, via a wireless controller of the gateway, a scan; obtaining identifiers for a plurality of construction assets within a range of the gateway based on scan results for the scan, wherein at least one construction asset in the plurality of construction assets is not associated with a user account maintained by a backend server; and transmitting, to the backend server, an identifier for the user account and the identifiers for the plurality of construction assets.

[0019] According to some example aspects, the method further comprises: receiving, from a user device, a command to perform the scan, wherein performing the scan is based on the command.

[0020] According to some example aspects, the gateway comprises a smartphone, and the method further comprises: receiving user input indicative of the scan, wherein performing the scan is based on the user input.4WBD (US) 4911-1825-7051

[0021] According to some example aspects, performing the scan comprises receiving a plurality of advertisement signals emitted by the plurality of construction assets, wherein the plurality of advertisement signals include the identifiers for the plurality of construction assets.

[0022] According to some example aspects, the method further comprises: receiving, from the backend server, an indication that the at least one construction asset has been associated with the user account.

[0023] According to some example aspects, the gateway comprises a smartphone, and the method further comprises: receiving, as user input, information pertaining to the at least one construction asset; and transmitting, to the backend server, the information pertaining to the at least one construction asset for association with the at least one construction asset in the user account.

[0024] According to some example aspects, the method further comprises: transmitting, to the backend server, a request for a graphical user interface (GUI) for entering the information pertaining to the at least one construction asset; receiving, from the backend server and based on the request, graphical data; and presenting the GUI based on the graphical data, wherein the GUI receives the information pertaining to the at least one construction asset.

[0025] According to some example aspects, the identifiers for the plurality of construction assets comprise medium access control (MAC) addresses.

[0026] According to some example aspects, the plurality of construction assets comprises at least one of tools or battery packs.

[0027] According to another aspect, the disclosure is generally directed to a gateway comprising: a wireless controller; a processor; and memory storing instructions that, when executed by the processor, cause the processor to implement the method as in any of the preceding aspects.5WBD (US) 4911-1825-7051

[0028] According to another aspect, the disclosure is generally directed to an apparatus comprising means for implementing a method as in any of the preceding aspects.

[0029] According to another aspect, the disclosure is generally directed to a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of the preceding aspects.

[0030] According to another aspect, the disclosure is generally directed to a computer program product for implementing a method as in any of the preceding aspects.

[0031] According to one aspect, the disclosure is generally directed to a method for tracking power tool emissions, comprising: receiving, from a gateway, indications of runtimes of a plurality of power tools that are powered via electricity from a power grid and an indication of a location of the plurality of power tools; obtaining, based on the indication of the location of the plurality of power tools, an estimate of emissions associated with the power grid; calculating at carbon dioxide equivalent emissions of the plurality of power tools over a period of time based on the indications of the runtimes, energy consumptions of the plurality of power tools, and the estimate of the emissions associated with the power grid; and presenting a graphical user interface (GUI) that depicts graphical information pertaining to the carbon dioxide equivalent emissions of the plurality of power tools.

[0032] According to some example aspects, obtaining the estimate of the emissions associated with the power grid comprises: determining, based on the location of the plurality of power tools, a geographic region that encompasses the location of the plurality of power tools; transmitting, to a power profde service, an indication of the geographic region; and receiving, from the power profde service, the estimate of the emissions associated with the power grid based on the indication of the geographic region.6WBD (US) 4911-1825-7051

[0033] According to some example aspects, the energy consumptions of the plurality of power tools comprise at least one of actual energy consumptions of the plurality of power tools received from the gateway or estimated energy consumptions of the plurality of power tools.

[0034] According to some example aspects, presenting the GUI comprises: transmitting, to a user device, data that causes the user device to present the GUI on a display of the user device.

[0035] According to some example aspects, the plurality of power tools comprises a first power tool of a first type and a second power tool of a second type, and wherein the GUI includes a window depicting a first carbon dioxide equivalent emission of the first power tool of the first type and a second carbon dioxide equivalent emission of the second power tool of the second type.

[0036] According to some example aspects, the GUI depicts a total carbon dioxide equivalent emission of the plurality of power tools for the period of time.

[0037] According to some example aspects, the method further comprises: calculating a volume of gasoline that would be consumed if the plurality of power tools were gasoline-powered based on the indications of the runtimes and the energy consumptions of the plurality of power tools; and calculating a carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered based on the volume of the gasoline, wherein the GUI depicts at least one of the volume of the gasoline or the carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered.

[0038] According to some example aspects, the plurality of power tools comprises a first power tool associated with a first assignment of a first type and a second power tool associated with a second assignment of a second type, and wherein the GUI includes a window depicting a first7WBD (US) 4911-1825-7051carbon dioxide equivalent emission for the first assignment of the first type and a second carbon dioxide equivalent emission for the second assignment of the second type.

[0039] According to some example aspects, the first type and the second type are included in a plurality of types of assignments comprising: a jobsite assignment; a project assignment; a work truck assignment; a job box assignment; or a warehouse assignment.

[0040] According to some example aspects, the period of time comprises at least one of: months of a year, days of a week, or hours of a day, and wherein the GUI depicts a total carbon dioxide equivalent emission for at least one of: each month of the year, each day of the week, or each hour of the day.

[0041] According to some example aspects, the method further comprises: receiving, from a user device, a request for the carbon dioxide equivalent emissions of the plurality of power tools; and transmitting, to the user device based on the request, tabular data that includes the carbon dioxide equivalent emissions of the plurality of power tools.

[0042] According to some example aspects, the GUI includes a window that depicts: a number of the plurality of power tools; a total runtime of the plurality of power tools; a total carbon dioxide equivalent emission for the plurality of power tools; a volume of gasoline saved by using the plurality of power tools; and cost savings from using the plurality of power tools that are powered via the electricity from the power grid.

[0043] According to another aspect, the disclosure is generally directed to a computing system, comprising: a processor; and memory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of the preceding aspects.8WBD (US) 4911-1825-7051

[0044] According to another aspect, the disclosure is generally directed to an apparatus comprising means for implementing a method as in any of the preceding aspects.

[0045] According to another aspect, the disclosure is generally directed to a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of the preceding aspects.

[0046] According to another aspect, the disclosure is generally directed to a computer program product for implementing a method as in any of the preceding aspects.

[0047] According to one aspect, the disclosure is generally directed to a method performed by a backend server associated with a first organization for asset tracking on a jobsite, comprising: generating a mobile assignment comprising an indication of a first gateway and an indication of a construction asset, wherein the first gateway is associated with a vehicle, and wherein the first gateway is associated with the first organization; receiving, from a server associated with a second organization, an identifier for the construction asset and a location of the construction asset based on a detection of the construction asset by a second gateway associated with the second organization, wherein the location of the construction asset is outside of a range of the first gateway; and updating an asset status of the construction asset in the mobile assignment based on the identifier for the construction asset and the location of the construction asset.

[0048] According to some example aspects, the method further comprises: determining that the first gateway has failed to detect the construction asset; and transmitting, to the server associated with the second organization and based on the determination, the identifier for the construction asset, wherein receiving the location of the construction asset from the server is based on the transmitted identifier for the construction asset.9WBD (US) 4911-1825-7051

[0049] According to some example aspects, determining that the first gateway has failed to detect the construction asset comprises determining that the backend server has not received the location of the construction asset from the first gateway within a time interval.

[0050] According to some example aspects, determining that the first gateway has failed to detect the construction asset comprises receiving, from the first gateway, a message indicating that the first gateway has failed to detect the construction asset.

[0051] According to some example aspects, the first gateway is disposed in the vehicle or integrated into the vehicle.

[0052] According to some example aspects, the method further comprises: causing a graphical user interface (GUI) to be presented on a display of a user device, wherein the GUI indicates the updated asset status.

[0053] According to some example aspects, the second gateway comprises at least one of: a stationary gateway; a mobile gateway; a gateway integrated into a construction vehicle; or a public gateway.

[0054] According to some example aspects, the construction asset comprises at least one of a tool or a battery pack.

[0055] According to some example aspects, the identifier for the construction asset is associated with advertisement data emitted by the construction asset.

[0056] According to some example aspects, the vehicle, the first gateway, and the second gateway are located on the jobsite.

[0057] According to some example aspects, the method further comprises: establishing, prior to receiving the identifier for the construction asset and the location of the construction asset, a 10WBD (US) 4911-1825-7051geofence boundary for the jobsite; and comparing the location of the construction asset received from the server to the geofence boundary for the jobsite, wherein updating the construction asset status of the construction asset in the mobile assignment is based on the comparison.

[0058] According to some example aspects, updating the construction asset status of the construction asset based on the comparison comprises updating the construction asset status to indicate that the construction asset is in a wrong location on the jobsite.

[0059] According to some example aspects, updating the construction asset status of the construction asset based on the comparison comprises updating the construction asset status to indicate that the construction asset is not on the jobsite.

[0060] According to some example aspects, receiving the identifier for the construction asset and the location of the construction asset comprises receiving the identifier for the construction asset and the location of the construction asset via an application programming interface (API) exposed by the backend server to the server.

[0061] According to another aspect, the disclosure is generally directed to a backend server, comprising: a processor; and memory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of the preceding aspects.

[0062] According to another aspect, the disclosure is generally directed to an apparatus comprising means for implementing a method as in any of the preceding aspects.

[0063] According to another aspect, the disclosure is generally directed to a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of the preceding aspects.11WBD (US) 4911-1825-7051

[0064] According to another aspect, the disclosure is generally directed to a computer program product for implementing a method as in any of the preceding aspects.

[0065] According to one aspect, the disclosure is generally directed to a method comprising: generating a plurality of assignments, wherein the plurality of assignments includes an assignment of a central device to a first location in a jobsite, wherein the plurality of assignments further includes assignments for assets in the jobsite, the assignments for the assets including locations of the assets in the jobsite and audit frequencies for audits of the assets; receiving, from the central device located at the first location, audit statuses for the assets, the audit statuses being based on signals transmitted by peripheral devices associated with the assets, the signals being sensed by the central device; determining, based on the assignments for the assets, asset statuses for the assets; and providing a graphical user interface (GUI) that depicts graphical information about at least one of the audit statuses for the assets or the asset statuses for the assets.

[0066] In some example aspects, the asset statuses include at least one of: a first number of the assets that are available for deployment, a second number of the assets that are deployed, or a third number of the assets that are missing or lost based on non-receipt of a signal by the central device.

[0067] In some example aspects, the audit statuses include at least one of: a first number of the assets that have been sensed by the central device during an audit within the audit frequencies, a second number of the assets that require audit based on the assignments, a third number of the assets that are overdue for the audit, the third number of the assets being based on non-receipt of a signal by the central device during the audit within the audit frequencies, or a fourth number of the assets that are in a wrong location, the fourth number of the assets being based on a receipt of the signal by a second central device located at a second location.12WBD (US) 4911-1825-7051

[0068] In some example aspects, providing the GUI comprises transmitting, to a user device and over a network, data that causes the user device to present the GUI on a display of the user device.

[0069] In some example aspects, the GUI depicts a plurality of selectable categories associated with the asset statuses, wherein each of the plurality of selectable categories, when selected, causes information to be presented within the GUI pertaining to a subset of the assets belonging to a selectable category in the plurality of selectable categories, and wherein the plurality of selectable categories includes at least one of: available assets, deployed assets, missing assets, service needed assets, out for service assets, or lost assets.

[0070] In some example aspects, the GUI depicts a plurality of selectable categories associated with the audit statuses, wherein each of the plurality of selectable categories, when selected, causes information to be presented within the GUI pertaining to a subset of the assets belonging to a selectable category in the plurality of selectable categories, and wherein the plurality of selectable categories includes at least one of: audit assets, needs audit assets, overdue assets, or wrong location assets.

[0071] In some example aspects, the GUI further comprises a chart that depicts a first percentage of the assets corresponding to the audit assets, a second percentage of the assets corresponding to the needs audit assets, a third percentage of the assets corresponding to the overdue assets, and a fourth percentage of the asset corresponding to the wrong location assets.

[0072] In some example aspects, the method further comprises: obtaining, from a user device, data indicative of the plurality of assignments, wherein generating the plurality of assignments is based on the data indicative of the plurality of assignments.13WBD (US) 4911-1825-7051

[0073] In some example aspects, the central device comprises at least one of gateway or a user device.

[0074] In some example aspects, the plurality of assignments indicates that the assets are assigned to the central device.

[0075] In some example aspects, the plurality of assignments is associated with a plurality of user accounts stored in a memory.

[0076] In some example aspects, the assignment of the central device to the first location in the jobsite is a first assignment of a first central device to the first location in a first jobsite, the assignments for assets in the jobsite are first assignments for first assets in the first jobsite, the assignments for the assets including locations of the assets in the jobsite and audit frequencies for audits of the assets are first locations of the first assets in the first jobsite and first audit frequencies for audits of the first assets in the first jobsite, audit statuses for the assets based on signals transmitted by peripheral devices associated with the assets are first audit statuses for the first assets based on first signals transmitted by first peripheral devices associated with the first assets, asset statuses for the assets are first asset statuses for the first assets the graphical information is first graphical information, the plurality of assignments includes a second assignment of a second central device to a second location in a second jobsite, and wherein the plurality of assignments further includes second assignments for second assets in the second jobsite, the second assignments for the second assets including second locations of the second assets in the second jobsite and second audit frequencies for audits of the second assets, and the method further comprises: receiving, from the second central device located at the second location, second audit statuses for the second assets, the second audit statuses being based on second signals transmitted by second peripheral devices associated with the second assets, the second signals being sensed 14WBD (US) 4911-1825-7051by the second central device; and determining, based on the second assignments for the second assets, second asset statuses for the second assets, wherein the GUI further depicts second graphical information about at least one of the second audit statuses for the second assets or the second asset statuses for the second assets.

[0077] In some example aspects, the method further comprises: determining, based on the second audit statuses, that the second central device received a signal transmitted by a first asset associated with the first assignments corresponding to the first central device; determining that the first assignments and the second assignments are both associated with a same user account; and transmitting, to a user device and over a network, a message comprising at least one of: a first indication that the first asset has been sensed within the second job site, or a second indication of an option to reassign the first asset to the second assignments.

[0078] In some example aspects, the method further comprises: receiving, from the user device and over the network, a response to the message, the response indicating that the first asset is to be reassigned to the second assignments; and reassigning, based on the response, the first asset from the first assignments to the second assignments.

[0079] In some example aspects, the assets comprise at least one of power tools, power tool accessories, construction tools, or construction materials.

[0080] In some example aspects, the signals are periodically transmitted by the peripheral devices.

[0081] In some example aspects, the peripheral devices comprise wireless communication devices.15WBD (US) 4911-1825-7051

[0082] In some example aspects, the central device is associated with a sensing range, and wherein the central device senses the signals when the assets are within the sensing range associated with the central device.

[0083] According to another aspect, the disclosure is generally directed to a computing system, comprising a processor and memory storing instructions that, when executed by the processor, cause the processor to implement the method as in any of the preceding aspects.

[0084] According to another aspect, the disclosure is generally directed to a non-transitory computer readable storage medium comprising instructions that, when executed by a processor, cause the processor to implement the method as in any of the preceding aspects.

[0085] According to another aspect, the disclosure is generally directed to a system comprising means for implementing the method as in any of the preceding aspects.

[0086] According to another aspect, the disclosure is generally directed to a computer program product for implementing a method as in any of the preceding aspects.

[0087] According to one aspect, the disclosure is generally directed to a method comprising: obtaining an audit status for each of a plurality of construction assets associated with a user account; providing a graphical user interface (GUI) depicting a first view of a map indicating geographic locations of each of the plurality of construction assets; and responsive to receiving an indication of a selection of a location of a jobsite on the first view of the map, adjusting the GUI to depict a second view of the map indicating a subset of the plurality of construction assets associated with the jobsite and audit statuses for each construction asset of the subset, wherein the second view is a zoomed-in version of the first view.16WBD (US) 4911-1825-7051

[0088] In some example aspects, the method further comprises: receiving an indication of a selection of a first construction asset in the subset; and responsive to receiving the indication of the selection of the first construction asset, providing, within the GUI and overlaid on the map, a first window indicating an identifier for the first construction asset and a first audit status of the first construction asset.

[0089] In some example aspects, the first audit status comprises: an indication that the first construction asset is audited, requires an audit, is overdue, or is in a wrong location, a time of a most recent audit of the first construction asset, and an identifier for a gateway that performed the most recent audit of the first construction asset.

[0090] In some example aspects, the first audit status indicates that the first construction asset is in a wrong location, wherein the first construction asset is assigned to a first assignment, and the method further comprises: receiving an indication of a selection of a transfer button displayed within the first window; responsive to receiving the indication of the selection of the transfer button displayed within the first window, providing within the GUI and overlaid on the map, a second window including fields for transferring the first construction asset from the first assignment to a second assignment; and responsive to obtaining input data for the fields, transferring the first construction asset from the first assignment to the second assignment based on the input data for the fields.

[0091] In some example aspects, the input data for the fields comprises at least one of: an identifier for the second assignment, a date for transferring the first construction asset from the first assignment to the second assignment, an asset status for the first construction asset, a person responsible for the first construction asset, or notes pertaining to the first construction asset.17WBD (US) 4911-1825-7051

[0092] In some example aspects, the GUI further includes a window, displayed proximate to the map, indicating the audit status for each of the plurality of construction assets when the map is depicted in the first view, and wherein the window indicates a first audit status for each construction asset of the subset when the map is depicted in the second view.

[0093] In some example aspects, the GUI includes at least one of: an audit status type filter menu, an assignment filter menu, or a responsible person filter menu, the method further comprising: receiving an indication of a selection of at least one of: an audit status type from amongst a plurality of audit status types displayed within the audit status type filter menu, an assignment from amongst a plurality of assignments displayed within the assignment filter menu, or a responsible person from amongst a plurality of responsible persons displayed within the responsible person filter menu; and updating the GUI to remove a construction asset from the map that is not associated with the at least one of the audit status type, the assignment, or the responsible person.

[0094] In some example aspects, updating the GUI to remove the construction asset from the map occurs responsive to adjusting the GUI to depict the second view of the map.

[0095] In some example aspects, the jobsite corresponds to an assignment, and wherein the GUI further depicts a geographic boundary associated with the assignment.

[0096] In some example aspects, the plurality of construction assets includes at least one of: a power tool, a power tool accessory, a battery pack, a construction tool, or a construction material.

[0097] In some example aspects, providing the GUI comprises transmitting the GUI over a network to a user device.18WBD (US) 4911-1825-7051

[0098] In some example aspects, obtaining the audit status for each of the plurality of construction assets comprises receiving the audit statuses over a network from a gateway associated with the jobsite.

[0099] According to another aspect, the disclosure is generally directed to a computing system, comprising a processor and memory storing instructions that, when executed by the processor, cause the processor to implement the method as in any of the preceding aspects.

[0100] According to another aspect, the disclosure is generally directed to a non-transitory computer readable storage medium comprising instructions that, when executed by a processor, cause the processor to implement the method as in any of the preceding aspects.

[0101] According to another aspect, the disclosure is generally directed to a system comprising means for implementing the method as in any of the preceding aspects.

[0102] According to another aspect, the disclosure is generally directed to a computer program product for implementing a method as in any of the preceding aspects.

[0103] According to one aspect, the disclosure is generally directed to a method comprising: receiving, from a user device, an indication of a construction asset category and a service plan for the construction asset category for a user account; applying, for the user account, the service plan to each of a plurality of construction assets that belong to the construction asset category; determining, based on the service plan, that a construction asset in the plurality of construction assets on a jobsite is due for service; and transmitting, to the user device, a notification indicating that the construction asset is due for the service based on the determination that the construction asset is due for the service.19WBD (US) 4911-1825-7051

[0104] In some example aspects, the construction asset comprises a plurality of components that operate in conjunction with one another to provide a functionality, wherein the construction asset category and the service plan pertain to a component in the plurality of components, and wherein the notification indicates that the component is due for the service.

[0105] In some example aspects, the method further comprises: providing, to the user device, a graphical user interface (GUI) that includes a first field for the construction asset category and a second field for the service plan, wherein receiving the indication of the construction asset category and the service plan for the construction asset category is based on input set forth to the first field and the second field.

[0106] In some example aspects, the service plan indicates a time period, wherein the service plan is applied at a time instance, wherein determining that the construction asset is due for the service includes determining that a difference between a current time instance and the time instance is greater than or equal to the time period.

[0107] In some example aspects, the service plan indicates a threshold operational runtime, the method further comprising: receiving, from a gateway, an indication of an operational runtime of the construction asset, wherein determining that the construction asset is due for the service includes determining that the operational runtime of the construction asset is greater than the threshold operational runtime.

[0108] In some example aspects, the service plan indicates a time period, wherein the service plan is applied at a first time instance, wherein determining that the construction asset is due for the service includes: identifying a second time instance associated with a last service of the construction asset; and determining that a difference between the first time instance and the second time instance is greater than the time period.20WBD (US) 4911-1825-7051

[0109] In some example aspects, the method further comprises: receiving, from the user device, an indication of new construction asset that is to be associated with the user account as part of an onboarding process; determining, during the onboarding process, that the new construction asset belongs to the construction asset category; and applying, during the onboarding process, the service plan to the new construction asset based on the determination that the new construction asset belongs to the construction asset category.

[0110] In some example aspects, applying the service plan to each of the plurality of construction assets includes associating an identifier for each of the plurality of construction assets with the service plan.[OHl] In some example aspects, receiving the indication of the construction asset category and the service plan from the user device includes receiving the indication of the construction asset category and the service plan from a first user device, wherein transmitting the notification to the user device includes transmitting the notification to a second user device that is different from the first user device.

[0112] In some example aspects, the plurality of construction assets includes at least one of: a power tool, a power tool accessory, a battery pack, a construction tool, or a construction material.

[0113] In some example aspects, the method further comprises: receiving, from the user device, an identifier of a service provider associated with the service plan, wherein the notification includes the identifier of the service provider.

[0114] In some example aspects, the method further comprises: receiving, from the user device, a date at which the service was performed on the construction asset; and storing the date as a last competed service date for the construction asset.21WBD (US) 4911-1825-7051

[0115] According to another aspect, the disclosure is generally directed to a computing system, comprising a processor and memory storing instructions that, when executed by the processor, cause the processor to implement the method as in any of the preceding aspects.

[0116] According to another aspect, the disclosure is generally directed to a non-transitory computer readable storage medium comprising instructions that, when executed by a processor, cause the processor to implement the method as in any of the preceding aspects.

[0117] According to another aspect, the disclosure is generally directed to a system comprising means for implementing the method as in any of the preceding aspects.

[0118] According to another aspect, the disclosure is generally directed to a computer program product for implementing a method as in any of the preceding aspects.BRIEF DESCRIPTION OF THE DRAWINGS

[0119] The described embodiments and the advantages thereof may best be understood by reference to the following description taken in conjunction with the accompanying drawings. These drawings in no way limit any changes in form and detail that may be made to the described embodiments by one skilled in the art without departing from the spirit and scope of the described embodiments.

[0120] FIG. l is a block diagram that illustrates an example of a system for communicating data about a power tool via wireless communication network(s) in accordance with some aspects of the present disclosure.22WBD (US) 4911-1825-7051

[0121] FIG. 2 is a block diagram that illustrates an example of a backend server for communicating data about a power tool via wireless communication network(s) in accordance with some aspects of the present disclosure.

[0122] FIG. 3 is a block diagram that illustrates an example of a power tool that communicates data via wireless communication network(s) in accordance with some aspects of the present disclosure.

[0123] FIG. 4 is a block diagram that illustrates an example of a power tool that communicates data via wireless communication network(s) in accordance with some aspects of the present disclosure.

[0124] FIG. 5 is a block diagram that illustrates an example of a gateway that communicates data about a power tool via wireless communication network(s) in accordance with some aspects of the present disclosure.

[0125] FIG. 6 is a diagram illustrating an example of a battery pack in accordance with some aspects of the present disclosure.

[0126] FIG. 7 is a diagram illustrating an example of a user device in accordance with some aspects of the present disclosure.

[0127] FIG. 8 is a diagram that illustrates a top-down view of an example of jobsites in accordance with some aspects of the present disclosure.

[0128] FIG. 9 is a communication flow diagram illustrating example communications between construction assets, a gateway, a backend server, and a user device for mass onboarding of construction assets in accordance with some aspects of the present disclosure.

[0129] FIG. 10 is a diagram illustrating an example of mass onboarding of assets via scanning markers of the assets in accordance with some aspects of the present disclosure.23WBD (US) 4911-1825-7051

[0130] FIG. 11 is a diagram illustrating another example of mass onboarding of assets via scanning markers of the assets in accordance with some aspects of the present disclosure.

[0131] FIG. 12 is a diagram illustrating an example of mass onboarding of assets via detecting advertisement signals of the assets in accordance with some aspects of the present disclosure.

[0132] FIG. 13 is a diagram illustrating another example of mass onboarding of assets via detecting advertisement signals of the assets in accordance with some aspects of the present disclosure.

[0133] FIG. 14 is a diagram illustrating an example of onboarding a kit and / or a pallet of assets via a scan in accordance with some aspects of the present disclosure.

[0134] FIG. 15 is a communication flow diagram illustrating example communications between power tools, a gateway, a backend server, and a user device for calculating and displaying carbon dioxide equivalent (CChe) emissions of the power tools in accordance with some aspects of the present disclosure.

[0135] FIG. 16 is a diagram illustrating an example of a graphical user interface (GUI) for displaying CChe emissions of the power tools in accordance with some aspects of the present disclosure.

[0136] FIG. 17 is a diagram illustrating another example of a GUI for displaying CChe emissions of the power tools in accordance with some aspects of the present disclosure.

[0137] FIG. 18 is a communication flow diagram illustrating example communications between a construction asset, a first gateway associated with both a first organization and a vehicle, a second gateway associated with a second organization, a backend server associated with the first organization, a server associated with the second organization, and a user device for tracking a status of the construction asset in accordance with some aspects of the present disclosure.24WBD (US) 4911-1825-7051

[0138] FIG. 19A is a diagram illustrating an example of a jobsite including a first gateway associated with a first organization and a second gateway associated with a second organization at a first time instance in accordance with some aspects of the present disclosure.

[0139] FIG. 19B is a diagram illustrating an example of a jobsite including a first gateway associated with a first organization and a second gateway associated with a second organization at a second time instance in accordance with some aspects of the present disclosure.

[0140] FIG. 20 is a decision flow diagram illustrating example decisions for tracking a status of an asset in accordance with some aspects of the present disclosure.

[0141] FIG. 21 is a decision flow diagram illustrating example decisions for tracking a status of an asset in accordance with some aspects of the present disclosure.

[0142] FIG. 22 is a decision flow diagram illustrating example decisions for tracking a status of an asset in accordance with some aspects of the present disclosure.

[0143] FIG. 23 is a diagram illustrating an example of a GUI for adding an assignment in accordance with some aspects of the present disclosure.

[0144] FIG. 24 is a diagram illustrating an example of a GUI for adding details to a fixed assignment in accordance with some aspects of the present disclosure.

[0145] FIG. 25 is a diagram illustrating another example of a GUI for adding details to a fixed assignment in accordance with some aspects of the present disclosure.

[0146] FIG. 26 is a diagram illustrating of a GUI for adding details to a mobile assignment in accordance with some aspects of the present disclosure.

[0147] FIG. 27 is a communication flow diagram that illustrates example communications between a first asset including a first peripheral device, a first central device, a backend server,25WBD (US) 4911-1825-7051and a user device for asset and audit status management in accordance with some aspects of the present disclosure.

[0148] FIG. 28 is a diagram illustrating an example of a decision flow for asset and audit status management in accordance with some aspects of the present disclosure.

[0149] FIG. 29 is a diagram illustrating an example of a GUI for asset and audit status management in accordance with some aspects of the present disclosure.

[0150] FIG. 30 is a diagram illustrating an example of a GUI for asset status management in accordance with some aspects of the present disclosure.

[0151] FIG. 31A is a diagram illustrating an example of a GUI for viewing asset details in accordance with some aspects of the present disclosure.

[0152] FIG. 3 IB is a diagram illustrating an example of a GUI for viewing assignment details in accordance with some aspects of the present disclosure.

[0153] FIG. 32 is a diagram illustrating an example of a GUI for viewing an audit history of an asset in accordance with some aspects of the present disclosure.

[0154] FIG. 33 is a diagram illustrating an example of a GUI for viewing audit statuses in accordance with some aspects of the present disclosure.

[0155] FIG. 34 is a communication flow diagram that illustrates example communications between construction assets, a gateway, a backend server, and a user device for presenting a GUI that depicts a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0156] FIG. 35 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.26WBD (US) 4911-1825-7051

[0157] FIG. 36 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0158] FIG. 37 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0159] FIG. 38 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0160] FIG. 39 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0161] FIG. 40 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0162] FIG. 41 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0163] FIG. 42 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.27WBD (US) 4911-1825-7051

[0164] FIG. 43 is a diagram illustrating an example of a GUI for depicting a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0165] FIG. 44 is a communication flow diagram that illustrates example communications between construction assets, a gateway, a backend server, and a user device for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0166] FIG. 45 is a diagram illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0167] FIG. 46 is a diagram illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0168] FIG. 47A is a diagram illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0169] FIG. 47B is a diagram illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0170] FIG. 48 is a diagram illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0171] FIG. 49 is a flow diagram of a method performed by a backend server for asset onboarding in accordance with some aspects of the present disclosure.

[0172] FIG. 50 is a flow diagram of a method performed by a gateway for asset onboarding in accordance with some aspects of the present disclosure.

[0173] FIG. 51 is a flow diagram of a method performed by a backend server for tracking power tool emissions in accordance with some aspects of the present disclosure.28WBD (US) 4911-1825-7051

[0174] FIG. 52 is a flow diagram of a method performed by a backend server associated with a first organization for asset tracking on a jobsite in accordance with some aspects of the present disclosure.

[0175] FIG. 53 is a flow diagram of a method of asset and audit status management in accordance with some aspects of the present disclosure.

[0176] FIG. 54 is a flow diagram of a method for presenting a GUI that depicts a map of construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure.

[0177] FIG. 55 is a flow diagram of a method for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0178] FIG. 56 illustrates a diagrammatic representation of a machine in an example form of a computer system that may perform one or more of the operations described herein in accordance with some aspects of the present disclosure.29WBD (US) 4911-1825-7051DETAILED DESCRIPTION

[0179] At a jobsite (e.g., a construction site), many different types of tools (e.g., power tools), related accessories (e g., power tool battery packs, battery pack chargers, tool storage and / or transportation constructs, lighting elements, tool adapters, supports, etc.), and other construction supplies may be used at various times and may collectively be referred to as assets associated with a jobsite. For example, for a large scale construction project, hundreds or thousands of tools may be utilized. Tracking locations and statuses of such assets may be challenging. For example, during the course of a construction project, a tool may be misplaced or stolen. Existing approaches to tracking tool locations may be designed on an individual user basis and may not scale appropriately for enterprise users. Furthermore, existing approaches may present information associated with jobsite assets in a table format, which may be frustrating to easily view from a user experience perspective. Some construction devices / assets (e.g., power tools) may be capable of communicating their locations and statuses (as well as other information) over a wireless communication protocol to one or more devices (e.g., a central device, such as a gateway or a user device). In an example, a gateway may then communicate the location and statuses of the construction devices / assets to a backend server which maintains details records of whether the construction devices / assets are located in a correct location.

[0180] An onboarding process may be performed in order to track a location of a construction asset when the construction asset is eventually deployed on a jobsite. The onboarding process may involve associating an identifier for the construction asset with a user account maintained by a backend server. One approach to onboarding may be to pair a construction asset (e.g., a power tool) with a mobile device (e.g., via a wireless communication protocol) in order for the mobile device to obtain the identifier for the construction asset. The mobile device may then transmit the30WBD (US) 4911-1825-7051identifier for the construction asset to the backend server. The backend server may then associate the identifier for the construction asset with a user account. However, this approach may be time consuming when a large number of construction assets (e.g., hundreds, thousands, etc.) are to be onboarded. Moreover, performing the pairing process a large number of times may be associated with a relatively large use of computing resources of the mobile device.

[0181] In some aspects, the present disclosure addresses the above-noted and other deficiencies by describing techniques for mass onboarding of construction assets via a scan performed by a gateway. In an example, construction assets may emit advertisement signals that include / indicate identifiers for the construction assets (e.g., MAC addresses of the construction assets). A user may initiate a scan (e.g., a Bluetooth® Low Energy (BLE) scan) on a mobile phone and / or a gateway to detect construction assets with a scanning range of the mobile phone and / or the gateway. The scan may cause the mobile phone and / or the gateway to detect the identifiers for the construction assets included in / indicated by the advertisement signals. The mobile phone and / or the gateway may transmit (and a backend server may receive) the identifiers for the construction assets and an identifier for a user account associated with the user. The backend server may compare the identifiers for the construction assets to existing construction assets associated with the user account and existing construction assets associated with other user accounts maintained by the backend server. If the scanned construction assets are not associated with the any user account, the backend server may add the scanned construction assets to the user account. Furthermore, in some aspects, the backend server may look up additional information (e.g., model numbers, build dates, etc.) about the scanned construction assets in a manufacturing log based on the identifiers for the scanned construction assets. The backend server may automatically add the additional information about the scanned construction assets to the user account.31WBD (US) 4911-1825-7051

[0182] In an example, a gateway performs, via a wireless controller of the gateway, a scan. The gateway obtains identifiers for a plurality of construction assets within a range of the gateway based on scan results for the scan, wherein at least one construction asset in the plurality of construction assets is not associated with a user account maintained by a backend server. The gateway transmits, to the backend server, an identifier for the user account and the identifiers for the plurality of construction assets. The backend server receives, from a gateway, an identifier for a user account and identifiers for a plurality of construction assets detected by the gateway within a range of the gateway, wherein the user account is maintained by the backend server. The backend server determines that at least one construction asset in the plurality of construction assets is not associated with the user account based on the identifier for the user account and the identifiers for the plurality of construction assets. The backend server associates an identifier for the at least one construction asset with the user account based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the user account.

[0183] As discussed herein, the present disclosure provides an approach that simplifies an onboarding process for a construction asset. Rather than having to individually pair each construction asset to a mobile device as part of the onboarding process, the approach described above may obtain identifiers for construction assets at one time via a scan, which reduces an amount of time to onboard the construction assets. Furthermore, the approach described above may reduce usage of computing resources of a mobile device / gateway compared to the individual pairing process described above.

[0184] Power tools are increasingly being powered by electricity (as opposed to gasoline) for cost reasons and / or environmental reasons. For example, a power tool that is powered by electricity may produce less greenhouse gas emissions than greenhouse gas emissions produced by an32WBD (US) 4911-1825-7051equivalent power tool powered by gasoline. However, determining an exact amount of the emissions may be challenging, as different power grids that can provide power to a power tool may be associated with different amounts of emissions, which in turn affects emissions of the power tool. Furthermore, presenting such an information to a user for a large quantity of power tools in an intelligible manner may be challenging.

[0185] In some aspects, the present disclosure addresses the above-noted and other deficiencies by describing techniques for providing visibility of carbon dioxide (CO2) emissions and / or carbon dioxide equivalent (CChe) emissions of power tools and equivalent savings from gasoline powered power tools. A backend server may use a construction asset runtime and energy used (if available) along with grid emissions and equivalent gas runtime to calculate CO2 emissions and / or CChe emissions. The backend server may cause the CO2 emissions and / or CChe emissions and equivalent gasoline savings to be presented in a dashboard form on a user device for analysis by an end user. Furthermore, to facilitate the analysis, the user device may download, from the backend server, a copy of the aforementioned emissions and gasoline savings data in tabular form, such as in a comma-separated values (CSV) file and / or a spreadsheet file.

[0186] In an example, a computing system (e.g., a backend server) receives, from a gateway, indications of runtimes of a plurality of power tools that are powered via electricity from a power grid and an indication of a location of the plurality of power tools. The computing system (e.g., a backend server) obtains, based on the indication of the location of the plurality of power tools, an estimate of emissions associated with the power grid. The computing system (e.g., a backend server) calculates a carbon dioxide equivalent emissions of the plurality of power tools over a period of time based on the indications of the runtimes, energy consumptions of the plurality of power tools, and the estimate of the emissions associated with the power grid. The computing33WBD (US) 4911-1825-7051system (e.g., a backend server) presents a graphical user interface (GUI) that depicts graphical information pertaining to the carbon dioxide equivalent emissions of the plurality of power tools.

[0187] As discussed herein, the present disclosure provides an approach that improves the presentation of emissions data associated with power tools. The approach described herein provides for a GUI that includes emissions information for power tools that can be readily understood by a user and that can be accessed through an application used to manage the power tools.

[0188] Many different construction assets (e.g., power tools) may be used to perform a construction job on a jobsite. Oftentimes, the construction assets may be manufactured by different organizations. Organizations may use different ecosystems (e.g., servers and gateways) to track their respective construction assets based on signals emitted by their respective construction assets. However, the different ecosystems may not be configured to exchange data with one another. Thus, tracking a status of a construction asset on a jobsite that includes construction assets manufactured by different organizations may be challenging.

[0189] In some aspects, the present disclosure addresses the above-noted and other deficiencies by describing techniques for tracking a status of a construction asset (e.g., a power tool) on a jobsite using gateways associated with different organizations. In an example, a construction asset and a mobile gateway (e.g., a gateway disposed in and / or integrated into a vehicle) associated with a first organization are assigned to a mobile assignment maintained by a backend server associated with the first organization. The mobile gateway may track a status of the construction asset based on an advertisement signal emitted by the construction asset. The first organization may share, with a second organization, details pertaining to a format of the advertising signal. The first organization may also expose an API that may be used to communicate with the backend server.34WBD (US) 4911-1825-7051During the course of a construction job, the construction asset may be moved outside of a range of the mobile gateway and / or the mobile gateway may move away from the construction asset such that the mobile gateway no longer detects the advertisement signal emitted by the construction asset. A third party gateway (associated with the second organization) on the jobsite may detect the advertisement signal based on the details pertaining to the format of the advertising signal shared by the first organization with the second organization. Detecting the advertisement signal may include detecting an identifier for the construction asset. The third party gateway may transmit the identifier for the construction asset and a location of the third party gateway to a server associated with the second organization. The server may then transmit the identifier for the construction asset and the location of the third party gateway to the backend server using the exposed API. The backend server may then update a status of the construction asset based on the identifier for the construction asset and the location of the third party gateway.

[0190] In an example, a backend server associated with a first organization generates a mobile assignment comprising an indication of a first gateway and an indication of a construction asset, wherein the first gateway is associated with a vehicle, and wherein the first gateway is associated with the first organization. The backend server receives, from a server associated with a second organization, an identifier for the construction asset and a location of the construction asset based on a detection of the construction asset by a second gateway associated with the second organization, wherein the location of the construction asset is outside of a range of the first gateway. The backend server updates an asset status of the construction asset in the mobile assignment based on the identifier for the construction asset and the location of the construction asset.35WBD (US) 4911-1825-7051

[0191] As discussed herein, the present disclosure provides an approach that improves tool tracking on a jobsite. For example, the above-described approach may enable a construction asset to be tracked on a jobsite that includes construction assets and gateways associated with different organizations. Additionally, the above-described approach may reduce instances of construction assets being lost on a jobsite, as gateways associated with the different organizations may be utilized to track construction assets.

[0192] The present disclosure addresses the above-noted and other deficiencies by implementing a site manager which can include systems and methods for asset and audit status management. The site manager may be executed by a backend server. The site manager may generate assignments for a jobsite (e.g., an under-construction building, a building or work area under repair / service / preparation, a staging area for asset storage and / or distribution such as a warehouse, headquarters, point of service, etc.) The assignments may include a central device (e.g., a gateway device, such as an Intemet-of-Things (loT) device, a smartphone that includes an application for tracking, etc.) and assets (e.g., construction tools and related accessories, a vehicle, a trailer, another mobile device or mobile construct, etc.), where the assignments indicate that the central device and the assets are linked. The assignments may also include expected locations of the central device and the assets in the jobsite. The assignments may also include an asset status for each asset (e.g., available, deployed, missing, etc.). Each asset may include or be coupled to a peripheral device (e.g., a wireless communication device) that periodically emits / broadcasts / transmits a signal that may be detected / sensed / received by the central device in the jobsite. The signal may include an identifier for the asset / peripheral device. The central device may determine an audit status for each asset based on the signal. An audit may refer to ascertaining whether an asset is in an expected location. For instance, if the central device senses a signal from36WBD (US) 4911-1825-7051an asset within a time duration defined by an audit frequency (e g., once an hour), the central device may determine the asset status for the asset to be “audited.” If the central device does not sense a signal from the asset within the time duration, the central device may determine the asset status for the asset to be “overdue” or “out of compliance”. If another central device located at a different location senses the signal, the asset status for the asset may be “wrong location.” The central device may transmit the asset status to the backend server that executes the site manager. The site manager may cause a graphical user interface (GUI) to be presented on a display of a user device, where the GUI depicts graphical information pertaining to the asset status of the asset and / or the audit status of the asset so as to enable the user to visually track both asset statuses and audit statuses in the same place.

[0193] In an example, a processor generates a plurality of assignments, where the plurality of assignments includes an assignment of a central device to a first location in a jobsite, where the plurality of assignments further includes assignments for assets in the jobsite, the assignments for the assets including locations of the assets in the jobsite and audit frequencies for the assets. The processor receives, from the central device located at the first location, audit statuses for the assets, the audit statuses being based on signals transmitted by peripheral devices associated with the assets, the signals being sensed by the central device. The processor determines, based on the assignments for the assets, asset statuses for the assets. The processor provides a graphical user interface (GUI) that depicts graphical information about at least one of the audit statuses for the assets or the asset statuses for the assets.

[0194] As discussed herein, the present disclosure provides an approach that improves the operation of a computer system by reducing an amount of input processed by the computer system to present asset statuses and audit statuses for assets. Moreover, by receiving audit statuses from37WBD (US) 4911-1825-7051a central device, the computer system may reduce an amount of input used to track assets in comparison to manual auditing approaches.

[0195] As discussed herein, tracking asset statuses and / or audit statuses of construction assets on a jobsite may be challenging. The present disclosure addresses the above-noted and other deficiencies by implementing a GUI that includes a map that indicates locations of construction assets and statuses of the construction assets associated with a user. In an example, the GUI may be part of a site manager as described herein. The GUI may include a panel that enables the user (e.g., an enterprise user) to obtain a list of all construction assets that are visible on the map. The GUI may include several filters that enable the user to filter construction assets displayed in the map by assignment, audit status, and / or a responsible party. The filters enable a user to filter for construction assets that have been assigned to select individuals and / or select assignments. The filters also enable the user to filter construction assets by audit status so that the user can view all construction assets that have been flagged as lost and / or stolen, or all construction assets that have been unassigned, in a single screen. As the user zooms in / out on the map, the listing of the construction assets with the applied filters is automatically updated.

[0196] In an example, a processor obtains an audit status for each of a plurality of construction assets associated with a user account. The processor provides a graphical user interface (GUI) depicting a first view of a map indicating geographic locations of each of the plurality of construction assets. Responsive to receiving an indication of a selection of a location of a jobsite on the first view of the map, the processor adjusts the GUI to depict a second view of the map indicating a subset of the plurality of construction assets associated with the jobsite and audit statuses for each construction asset of the subset, wherein the second view is a zoomed-in version of the first view.38WBD (US) 4911-1825-7051

[0197] As discussed herein, the present disclosure provides an approach that improves the operation of a computer system by reducing an amount of input processed by a computer system to display construction assets of interest within a geographical area. Moreover, the present disclosure improves the technological field of construction asset tracking / management by providing a GUI that enables a user to track locations and audit statuses of construction assets on a jobsite in a single view.

[0198] Certain construction assets (or components thereof) may undergo regular service in order to continue to function properly. For instance, various components of a heavy duty tool such as a concrete tool may undergo maintenance at set intervals. Tracking and monitoring service plans associated with construction assets (e.g., power tools) on a jobsite may be challenging. Some construction inventory management systems may enable a user to interact with a dashboard associated with individual tools and set a service schedule for each tool individually (i.e., service plans for tools are maintained at an individual tool level), which may not be suitable for enterprise users that may own and / or manage a large number of tools (e.g., thousands).

[0199] The present disclosure addresses the above-noted and other deficiencies by enabling a user to create a service plan and apply the service plan to multiple construction assets (e.g., power tools) belonging to a particular category in an inventory list of a user. For instance, in a service plan set up GUI, the user may specify a category of construction assets that the service plan will apply to (e.g., all torque ranges, all concrete screeds, etc.). The user also sets a schedule (e.g., monthly, after one-hundred hours of runtime, after a certain number of run cycles, etc.) at which the category of construction assets will be serviced. Once the schedule is set, all construction assets that fall within the designated category are automatically assigned to the service plan. For each construction asset, the date of the last service is saved and is automatically compared to the39WBD (US) 4911-1825-7051schedule associated with the service plan, and the date of next service is accordingly scheduled. Furthermore, if a new construction asset (e.g., a new tool) is onboarded that falls within the designated category, the service plan is set up for the new construction asset at the time of onboarding. The service plan may keep track of a service schedule for each construction asset within a particular category, and provide notifications / reminders to user devices when service is due. The user can also update a service schedule for all tools in the designated category with ease using a single interface.

[0200] In an example, a processor receives, from a user device, an indication of a construction asset category and a service plan for the construction asset category for a user account. The processor applies, for the user account, the service plan to each of a plurality of construction assets that belong to the construction asset category. The processor determines, based on the service plan, that a construction asset in the plurality of construction assets on a jobsite is due for service. The processor transmits, to the user device, a notification indicating that the construction asset is due for the service based on the determination that the construction asset is due for the service.

[0201] As discussed herein, the present disclosure provides an approach that improves the operation of a computer system by reducing an amount of input processed by a computing system to assign construction assets (e.g., power tools) to service plans. Moreover, the present disclosure improves the technological field of construction asset tracking / management by enabling service plans to be applied to all construction assets of a particular category (as opposed to manually setting a service plan for each individual construction asset).

[0202] FIG. 1 is a block diagram 100 that illustrates an example of a system for communicating data about a power tool via wireless communication network(s) in accordance with some aspects of the present disclosure. In some aspects, the system illustrated in FIG. 1 may also be used for 40WBD (US) 4911-1825-7051asset and audit status management. The system includes a first asset 102 and an Nth asset 104, where N is a positive integer greater than one. The first asset 102 and the Nth asset 104 may be collectively referred to as “the plurality of assets 102-104.” The plurality of assets 102-104 may be located at (and / or should be located at) different locations on a jobsite (e.g., an underconstruction building, a building or work area under repair / service / preparation, a staging area for asset storage and / or distribution such as a warehouse, headquarters, point of service, another structure, etc.). For a detailed description of various assets, the network architecture associated with the assets, and the type of data collected and communicated via the assets, reference is made to International Application No. PCT / US2024 / 053075, filed October 25, 2024, which is incorporated herein by reference in its entirety. As used herein, the term “asset” and “construction asset” may be used interchangeably.

[0203] The plurality of assets 102-104 may be or include construction tool(s), construction device(s), construction material(s), and / or vehicle(s) (e.g., a trailer). In an example, the construction tool(s) may include power tool(s) and related accessories. In an example, the plurality of assets 102-104 may be or include battery pack(s) that provide power to the power tool(s). In an example, the plurality of assets 102-104 may be or include corded tools and / or battery powered tools. In an example, the plurality of assets 102-104 may be or include tools used in construction applications and / or do-it-yourself (DIY) applications. In an example, the plurality of assets 102-104 may be or include concrete tools (e.g., a rammer, a plate compactor, a screed, a concrete saw, a concrete drill, etc ), woodworking tools (e.g., a circular saw, a reciprocating saw, a table saw, a miter saw, a router, etc.), metalworking tools (e.g., a grinder, a die grinder, a cut-off tool, a polisher, etc.), fastening tools (e.g., an impact tool, a drill, a hammer drill, an impact wrench, a ratchet, etc.), nailing tools (e.g., a concrete nailer, a roofing nailer, a finishing nailer, etc.), work light products,41WBD (US) 4911-1825-7051lasers, etc. In some aspects, the plurality of assets 102-104 may be or include construction vehicles (e.g., trucks, earth moving equipment, lifting equipment, etc.).

[0204] The first asset 102 may include and / or be coupled to a first peripheral device 106 and the Ath asset 104 may include and / or be coupled to an Ath peripheral device 108. The first peripheral device 106 and the Ath peripheral device 108 may be collectively referred to as “the plurality of peripheral devices 106-108.” In an example, the plurality of peripheral devices 106-108 may be or include wireless communication devices and / or wired communication devices. In an example, the plurality of peripheral devices 106-108 may be or include a Bluetooth® radio (e.g., a Bluetooth® Low Energy Radio), a long-range wireless communication radio (e.g., LoRaWAN, LPWAN, Wi-SUN, etc.), a wireless local area network (WLAN) radio, a cellular radio, etc. In some aspects, the plurality of peripheral devices 106-108 may be or include radio-frequency identification (RFID) tags. Some of the plurality of peripheral devices 106-108 may include a wireless controller and a transceiver mounted internally within the first asset 102, e.g., on a circuit board housed internally within the first asset 102. Additionally, and / or alternatively, some of the plurality of peripheral devices 106-108 may be removable modular units that can be selectively plunged into a compartment of one or more of the first asset 102. In other embodiments, some of the plurality of peripheral devices 106-108 may be tracking devices such as audit tags or audit chips, such as the commercially available DeWalt® DCE041 Tag or DEC042 Audit Chip, which can be removably coupled with any power tool, powered equipment, and / or unpowered products (e.g., ladders, hand tools, toolboxes, construction material, etc.)

[0205] In general, the first peripheral device 106 may be configured to transmit, broadcast, and / or emit a first signal 110 and the Ath peripheral device 108 may be configured to transmit, broadcast, and / or emit an Ath signal 112. The first signal 110 and the Ath signal 112 may be collectively42WBD (US) 4911-1825-7051referred to as “the plurality of signals 110-112.” The first signal 110 and / or the Nth signal 112 may be utilized for various purposes. For example, the first signal 110 and / or the 2Vth signal 112 may include operational information about power tools. In some aspects, the first signal 110 and / or the Mh signal 112 may be referred to as advertisement signals. In some aspects, the first signal 110 may be utilized for asset status and / or audit status purposes for the first asset 102 and the Nth signal 112 may be utilized for asset status and / or audit status purposes for the Nth asset 104. The first signal 110 and the Nth signal 112 may be collectively referred to as “the plurality of signals 110-112.” In some examples, where the first peripheral device 106 is configured with a Bluetooth® or long-range communication protocol, the first signal 110 may be an advertisement signal that is periodically broadcast. The advertisement signal may include a plurality of fields, including a first unique identification associated with the first peripheral device 106; a second unique identifier associated with a manufacturer of the first peripheral device 106; a third unique identifier associated with an owner and / or operator of the first peripheral device 106; and one or more fields including operating data related to the first asset 102. For examples and a detailed description, reference is made to International Application No. PCT / US2024 / 053075, filed on October 25, 2024, which is incorporated herein by reference in its entirety.

[0206] The system may include a first central device 114 and a backend server 116. The first central device 114 may be located at a first location on a first jobsite at which the plurality of assets 102-104 are located. In general, and as will be described in greater detail below, the first central device 114 may be configured to receive / detect / sense one or more of the plurality of signals 110-112, detect / sense an absence of one or more of the plurality of signals 110-112, and / or detect / sense signals from other assets. In some aspects, the first central device 114 may also be configured to utilize the plurality of signals 110-112 to transmit information about the first asset 102 (i.e., first43WBD (US) 4911-1825-7051asset information 118). In some aspects, the first central device 114 may also be configured to utilize the plurality of signals 110-112 to transmit first audit statuses 119 corresponding to the plurality of assets 102-104

[0207] The first central device 114 may be associated with a sensing range. The sensing range may be a distance from a location of the first central device 114 at which the first central device 114 is able to sense signals (or able to reliably sense signals). The sensing range may be based on a type of communication component (not illustrated in FIG. 1) used by the first central device 114 to detect / sense / receive signals. In an example, if an asset in the plurality of assets 102-104 is inside the sensing range of the first central device 114, the first central device 114 may be able to sense the asset, whereas if the asset in the plurality of assets 102-104 is outside of the sensing range of the first central device 114, the first central device 114 may not be able to sense the asset.

[0208] In an example, the first central device 114 may be or include a gateway (i.e., a gateway device). The gateway device may include a processor, a memory, and a wireless transceiver coupled to the processor. The wireless transceiver may be configured to receive / sense / detect one or more of the plurality of signals 110-112. In another example, the first central device 114 may be a device operated by a user, such as a smartphone or a tablet computing device. In an example, the first central device 114 may be or include the computer system 5600 (FIG. 56) or a portion thereof. In some aspects, the first central device 114 may be configured to detect a presence of one of the assets 102-104 in its proximity when the first central device 114 senses or receives one of the signals 110-112 transmitted by one of the peripheral devices 106-108 within a communication range of the first central device 114. In some examples, the first central device 114 may be configured to monitor and detect signals 110-112 in which the second unique identifier is correctly associated with the manufacturer of the first peripheral device 106 and / or the44WBD (US) 4911-1825-7051manufacturer of the first central device 114. Thus, wireless devices not associated with power tools and / or other products of the manufacturer of the first peripheral device 106 and / or the manufacturer of the first central device 114 may be ignored by the first central device 114. In some examples, the first central device 114 may be configured to monitor and detect signals 110- 112 in which the third unique identifier is correctly associated with the owner and / or operator of the first peripheral device 106 and / or the first central device 114. Thus, wireless devices not associated with the owner and / or operator of the first peripheral device 106 and / or the manufacturer of the first central device 114, such as the owner associated with a user account associated with these devices, may be ignored by the first central device 114.

[0209] In some aspects, the backend server 116 may be configured to receive the first asset information 118 from the first central device 114 (and / or from other central devices). In some aspects, the backend server 116 may be configured to receive the first audit statuses 119 from the first central device 114 (and / or from other central devices). In some aspects, the backend server 116 may be a cloud based computing platform. In some aspects, the backend server 116 may be or include the computer system 5600 (or a portion thereof). The backend server 116 may also be configured to assign the plurality of assets 102-104 and / or the first central device 114 to the first jobsite, where the assignment of the plurality of assets 102-104 and / or the first central device 114 to the first jobsite may be utilized for determining statuses of the plurality of assets 102-104 (i.e., asset statuses).

[0210] The system may also include a user device 120 operated by a user (e.g., a construction worker). In an example, the user device 120 may be or include a smartphone, a tablet computing device, a desktop computing device, a wearable computing device, and / or a laptop computing device. In some aspects, the user device 120 and the first central device 114 may be the same45WBD (US) 4911-1825-7051device (e.g., a smartphone). In some aspects, the user device 120 and the first central device 114 may be different devices (e.g., the user device 120 may be a smartphone and the first central device 114 may be a gateway). In some aspects, the user device 120 may be or include the computer system 5600 (or a portion thereof).

[0211] The backend server 116 may be configured to provide a GUI 123 to the user device 120. For example, the backend server 116 may be configured to transmit, over a network, data to the user device 120 which causes the user device 120 to present the GUI 123 on a display of the user device 120. The GUI 123 may present graphical information pertaining to information about assets. The user device 120 may be configured to receive interactions with the GUI 123 (i.e., “a GUI interaction 124”) from the user and to transmit an indication of the GUI interaction 124 to the backend server 116. Details pertaining to the GUI interaction 124 are described in greater detail below. The backend server 116 may update the GUI 123 based on the GUI interaction 124. For example, the backend server 116 may receive the indication of the GUI interaction 124 from the user device 120 and the backend server 116 may transmit additional data to the user device 120 based on the GUI interaction 124 that causes the user device 120 to update the GUI 123. In some aspects, the GUI 123 may present graphical information pertaining to the first audit statuses 119 for the plurality of assets 102-104 (and / or audit statuses for other assets) and / or asset statuses for the plurality of assets 102-104 (and / or asset statuses for the other assets).

[0212] The system may further include an A / th central device 126, where AT is a positive integer greater than one, and a second plurality of assets 128. The A / th central device 126 may be similar or identical to the first central device 114. For instance, in some aspects, the first central device 114 and the A th central device 126 may be the same type of device, that is, the first central device and the A / th central device 126 may be a first gateway and an A / th gateway, respectively. In some46WBD (US) 4911-1825-7051aspects, the first central device 114 may be a first type of device (e.g., a gateway) and the A / th central device 126 may be a second type of device (e.g., a smartphone).

[0213] The second plurality of assets 128 may be similar or identical to the plurality of assets 102-104. In some aspects, the second plurality of assets 128 may be different from the plurality of assets 102-104. In an example, the plurality of assets 102-104 may be utilized to construct / work upon a first portion of a structure on the jobsite (or a features of the jobsite) and the second plurality of assets 128 may be utilized to construct / work upon a second portion of the structure on the jobsite (or a feature of the jobsite or another jobsite). The second plurality of assets 128 may include and / or be coupled to second peripheral devices 130. The second peripheral devices 130 may be similar or identical to the plurality of peripheral devices 106-108.

[0214] The A / th central device 126 may be located at an A / th location at which the second plurality of assets 128 are located. In some aspects, theA / th location may be a location on the same jobsite at which the first central device 114 and the plurality of assets 102-104 are located (or should be located). In some other aspects, the A / th location may be a location at a second jobsite that is different from the jobsite at which the first central device 114 and the plurality of assets 102-104 are located. The A / th central device 126 may be configured to detect / sense / receive second signals 132 emitted / transmitted / broadcast by the second peripheral devices 130. The A / th central device 126 may be configured to utilize the second signals 132 to transmit information about the second plurality of assets 128 (i.e., asset information 122) to the backend server 116. The backend server 116 may also cause the GUI 123 to include information pertaining to the asset information 122. In some aspects, the A / th central device 126 may be configured to utilize the second signals 132 to transmit second audit statuses 134 to the backend server 116, where the second audit statuses 134 correspond to the second plurality of assets 128. The backend server 116 may also cause the GUI47WBD (US) 4911-1825-7051123 to include information pertaining to asset statuses of the second plurality of assets 128 and / or the second audit statuses 134 for the second plurality of assets 128.

[0215] FIG. 2 is a block diagram 200 that illustrates an example of a backend server 116 for communicating data about a power tool via wireless communication network(s) in accordance with some aspects of the present disclosure. In some aspects, the backend server may be used for asset and audit status management. The backend server 116 may include a processor 202 and memory 204. The memory 204 may store asset and audit tracking instructions 206 that, when executed by the processor 202, cause the processor 202 to implement functionality pertaining to asset and audit tracking as described herein. In some aspects, the asset and audit tracking instructions 206 may be referred to as a server-side site manager.

[0216] The memory 204 may further store a first user account 208 for a first user. In an example, the first user account 208 may be for an enterprise or another relatively large scale user or organization. In an example, the user device 120 (depicted in FIG. 1) may receive input from a user, where the input includes information to create the first user account 208. The user device 120 may transmit data indicative of the input to the backend server 116, and the backend server 116 may create the first user account 208 in the memory 204 based on the data.

[0217] The first user account 208 may be linked to first assignments 210 stored in the memory 204. In an example, the user device 120 (depicted in FIG. 1) may receive input from the user, where the input includes information to create the first assignments 210 and information indicative of the first user account 208. As will be described in greater detail below, information to create assignments (e.g., the first assignments 210) may include indication(s) of: jobsite(s), audit frequenc(ies), central device(s), and / or asset(s). The user device 120 may transmit data indicative of the input to the backend server 116, and the backend server 116 may create the first assignments48WBD (US) 4911-1825-7051210 in the memory 204 based on the data. In some aspects, the backend server 116 may additionally create the first assignments 210 based on data from construction planning software used to plan a construction job.

[0218] The first assignments 210 may include an indication of a first jobsite 212. The first jobsite 212 may include and / or be associated with a construction site or a construction project or another type of worksite. In some aspects, the first jobsite 212 may include geographic coordinates (e.g., a latitude and a longitude) of a construction site. In some aspects, the first jobsite 212 may include a set of geographic coordinates (e.g., sets of longitudes and latitudes) that define an area (e.g., a rectangular area, a circular area, etc.) of the construction site. In some aspects, the first jobsite 212 may include an address (e.g., a street name, a street number, a city, a state, and a zip code) of the construction site. In some aspects, the first jobsite 212 may include a description of a construction job (e.g., “Factory Construction at 123 Main Street”). In some aspects, the first jobsite 212 may correspond to an entirety of a construction job (e.g., constructing a factory). In some aspects, the first jobsite 212 may correspond to a portion of a construction job (e.g., installing plumbing in a factory).

[0219] The first assignments 210 may further include an indication of the first central device 114, an indication of the first asset 102, and an indication of the Mh asset 104. The first assignments 210 may indicate that the first asset 102 and the Mh asset 104 are assigned to the first central device 114 for audit purposes (described in greater detail below).

[0220] In some aspects, the indication of the first asset 102 and / or the indication of the Mh asset 104 may indicate expected locations of the first asset 102 and / or the Mh asset 104 in the first jobsite 212. In some aspects, the expected locations may be defined with respect to a distance from the first central device 114. For instance, an expected location of the first asset 102 may49WBD (US) 4911-1825-7051indicate that the first asset 102 is expected to be located within thirty meters of the first central device 114. In some aspects, the expected locations may be geolocation coordinates (e.g., sets of latitudes and longitudes). In some aspects, the expected locations may be addresses.

[0221] In some aspects, the indication of the first asset 102 and / or the indication of the / Vth asset 104 may include information about the first asset 102 and / or the Mh asset 104. Information about an asset (e.g., the first asset 102, the Mh asset 104, etc.) may include an image of the asset, a description of the asset, a model number of the asset, an inventory number, a category of the asset, a manufacturer of the asset, a person responsible for the asset, a serial number of the asset, a barcode for the asset, a purchase date of the asset, a registration date of the asset, historical data about the operational use of the asset, etc.

[0222] The first asset 102 and the Mh asset 104 may be associated with a first asset status 214 and Mh asset status 216, respectively, in the first assignments 210. An asset status may be indicative of a status of an asset. In an example, the first asset status 214 and / or the Mh asset status 216 may be or include available, deployed, missing, service needed, out for service, or lost. An asset (e.g., the first asset 102) that is / with a status of available may refer to an asset that is able to be used for a construction job. An asset that is / with a status of deployed may refer to an asset that is physically present on a jobsite. An asset that is / with a status of missing may refer to an asset that is not at an expected location of the asset, but that has not been determined to be lost. An asset referred to by / with a status of “service needed” may refer to an asset that is to undergo service in order for the asset to continue operating as intended and / or to comply with a jobsite / manufacturing policy. An asset that is / with a status of out for service may refer to an asset that is undergoing service. An asset that is / with a status of lost may refer to an asset that has not been determined to be at an expected location for the asset for a certain duration of time and that has not been detected at50WBD (US) 4911-1825-7051another location for the certain duration of time. In some aspects, the first asset status 214 and / or the Mh asset status 216 may be based on user input (e.g., input to the user device 120), the first signal 110 and / or the Mh signal 112, and / or the first audit statuses 119.

[0223] The first assignments 210 may include a first audit frequency 218. The first audit frequency 218 may define a time period at which assets (e.g., the first asset 102 and the / Vth asset 104) are to be audited. In an example, the first audit frequency 218 may be once a minute, once an hour, once a day, or once a week. An audit of an asset may refer to determining whether an asset is at an expected location of the asset. An audit may be based on signal(s) (e.g., the first signal 110 and the Mh signal 112) broadcast / transmitted / emitted by a peripheral device of an asset. In an example, if the first audit frequency 218 is once an hour, the first central device 114 may be expected to verify a location of the first asset 102 and the Mh asset 104 every hour.

[0224] Although the first audit frequency 218 has been described as being for the first asset 102 and the Nth asset 104, other possibilities are contemplated. In some aspects, the first asset 102 and the Mh asset 104 may each be assigned an individual audit frequency. For example, the first asset 102 may be assigned a first audit frequency and the Mh asset 104 may be assigned an Mh audit frequency, where the first audit frequency and the Mh audit frequency may be the same or different.

[0225] The first asset 102 and the Mh asset 104 may be associated with a first audit status 220 and an Mh audit status 222, respectively. The first audit status 220 and / or the Mh audit status 222 may be or may be included in the first audit statuses 119. In an example, the first audit status 220 may be based on receipt (or non-receipt) of the first signal 110 by the first central device 114 and the Mh audit status 222 may be based on receipt (or non-receipt) of the Mh signal 112 by the first central device 114. An audit status (e.g., the first audit status 220, the Mh audit status 222) may51WBD (US) 4911-1825-7051be audited, needs audit, overdue, or wrong location. An asset is audited when the asset has been confirmed to be in an expected location of the asset (e.g., based on receipt, by the first central device 114, of the first signal 110 transmitted / broadcast / emitted by the first peripheral device 106 of the first asset 102) within a time period defined by the first audit frequency 218. An asset is overdue for an audit when the asset has not been confirmed to be in an expected location of the asset within the time period defined by the first audit frequency 218 and the time period has expired. An asset is in the wrong location when the asset has been confirmed to be in an unexpected location of the asset (e.g., based on receipt, by the A / th central device 126, of a signal transmitted / broadcast / emitted by the first peripheral device 106 of the first asset 102) within the time period defined by the first audit frequency 218. An asset may need auditing when the asset has not yet been confirmed to be in the expected location of the asset during the time period defined by the first audit frequency 218, but remaining time still exists within the time period.

[0226] In some aspects, the first asset status 214 and / or the Ath asset status 216 may be updated based on the first audit status 220 and / or the Ath audit status 222, respectively. For example, if the first audit status 220 indicates that an audit for the first asset 102 is overdue, the first asset status 214 may be updated to be missing.

[0227] The first assignments 210 may be associated with / include a first type 232. In an example, the first type 232 may be fixed, mobile, or home. A fixed assignment (i.e., when the first type 232 is fixed) may refer to an assignment where an asset is used (e.g., a jobsite or a projection) and in which a gateway / central device associated with the asset is located at a fixed location. A mobile assignment (i.e., when the first type 232 is mobile) may refer to an assignment in which a gateway / central device associated with the asset is located on a moving vehicle (e.g., a truck, a52WBD (US) 4911-1825-7051van, etc.). A home assignment (i.e., when the first type 232 is home) may refer to an assignment for a place where an asset is stored (e.g., a warehouse, a tool crib, a store room, etc.).

[0228] The first user account 208 may also be linked to second assignments 224 stored in the memory 204. The second assignments 224 may be created in a manner similar to that described above with respect to the first assignments 210. The second assignments 224 may include an indication of a second jobsite 226 that is different from the first jobsite 212. In some aspects, the first jobsite 212 and the second jobsite 226 may be a first portion and a second portion, respectively, of a construction job or portions of other work performed on the second jobsite 226. In some aspects, the first jobsite 212 may be for a first construction job and the second jobsite 226 may be for a second construction job that is unrelated to the first construction job.

[0229] The second assignments 224 may further include an indication of the A / th central device 126 and an indication of the second plurality of assets 128. The second assignments 224 may indicate that the second plurality of assets 128 are assigned to the ATth central device 126 for audit purposes. The second assignments 224 may be associated with / include a second type 234. In an example, the second type 234 may be fixed, mobile, or home (described above).

[0230] In some aspects, the indication of the second plurality of assets 128 may indicate expected locations of each of the second plurality of assets 128 in the second jobsite 226. In some aspects, the expected locations may be defined with respect to a distance from the A / th central device 126. For instance, an expected location of each of the second plurality of assets 128 may indicate that each of the second plurality of assets 128 are expected to be located within twenty meters of the A th central device 126. In some aspects, the expected locations may be geolocation coordinates (e.g., sets of latitudes and longitudes). In some aspects, the expected locations may be addresses.53WBD (US) 4911-1825-7051

[0231] In some aspects, the indication of the second plurality of assets 128 may include information about each of the second plurality of assets 128. The second plurality of assets 128 may be associated with second asset statuses 225 and second audit statuses 227. The second asset statuses 225 may be similar to the first asset status 214 and / or the TVth asset status 216 described above. The second audit statuses 227 may be similar to the first audit status 220 and / or the / Vth audit status 222 described above. The second assignments 224 may include a second audit frequency 228. The second audit frequency 228 may be similar to the first audit frequency 218 described above.

[0232] The memory 204 may also store an TTh user account 230, where P is a positive integer greater than one. The th user account 230 may include assignment s) similar to those described above with respect to the first user account 208.

[0233] FIG. 3 is a block diagram 300 that illustrates an example of a power tool 302 that communicates data via wireless communication network(s) in accordance with some aspects of the present disclosure. In an example, the power tool 302 may be, may include, and / or may be associated with the first asset 102 and / or the first peripheral device 106.

[0234] The power tool 302 may include a motor 304. In an example, the motor 304 may be or include an electronically commutated brushless motor, a brush motor, a stepper motor, a direct current (DC) motor, a brushless DC motor, a universal motor, an induction motor, a reluctance motor, and / or a synchronous motor.

[0235] The power tool 302 may include position sensors 306. The position sensors 306 may be coupled to the motor 304. The position sensors 306 may be configured to output signals (i.e., “position signals”) corresponding to a rotational position of the motor 304. In an example, the54WBD (US) 4911-1825-7051position sensors 306 may be or include Hall sensors. Hall sensors may refer to magnetic sensors that detect a presence and a strength of a magnetic field.

[0236] The power tool 302 may include a motor control unit 308. The motor control unit 308 may be configured to control the motor 304. The motor control unit 308 may include a power module 310 and a control module 312. The power module 310 may include a power switch circuit 314 provided between a power source (not depicted in FIG. 3) of the power tool 302 (e.g., B+ and B-nodes of a battery back) and the motor 304. The power switch circuit 314 may be configured as an inverter circuit for regulating a supply of power to the motor 304.

[0237] The control module 312 may include a motor controller 316. The motor controller 316 may be a programmable processor configured to control the motor 304 to achieve a desired drive speed based on position signals from the position sensors 306. The control module 312 may include a gate driver 318 configured to drive gates of power switches in the power switch circuit 314 based on drive signals from the motor controller 316. The control module 312 may include a power supply regulator 320 that supplies DC voltage at appropriate voltage levels to the motor controller 316 and the gate driver 318. The DC voltage may be supplied by a battery pack (not depicted in FIG. 3) connected to the power tool 302. The motor controller 316 may be activated when the battery pack is connected to and powering the power tool 302. The motor controller 316 may receive signals such as the stack voltage and thermistor signals from the battery pack and the motor controller 316 may shut down supply of power from the battery pack in the event of a fault condition (e.g., over-temperature or under-voltage condition) based on the signals. In some aspects, the motor controller 316 may receive a data communication signal from the battery pack and the motor controller 316 may establish a designated communication line with the battery pack to transmit and / or receive data. The motor controller 316 may include a local memory 322. The55WBD (US) 4911-1825-7051motor controller 316 may be configured to record the data from the battery pack in the local memory 322.

[0238] The power tool 302 may include a trigger 324 and a tool element 326. When the trigger 324 is utilized (e.g., pressed, pulled, depressed, selected, etc. by a user, such as a construction worker), the motor control unit 308 may receive a signal which causes the power tool 302 to activate and to adjust a position and / or an orientation of the tool element 326 such that the power tool 302 performs a function for which the power tool 302 is configured. In an example, the tool element 326 may be or include a drill bit, a saw blade, a screwdriver tip, etc.

[0239] The power tool 302 may include a wireless communication module 328. The wireless communication module 328 may be connected to the motor controller 316. The wireless communication module 328 may be configured to wirelessly communicate various information to and / or from the motor controller 316. The wireless communication module 328 may include a wireless controller 330, memory 332, and a transceiver 334. A transceiver may refer to an electronic device that is a combination of a radio transmitter and a radio receiver.

[0240] In some aspects, the transceiver 334 may include a BLE unit 336 that is coupled to an antenna 338 to transmit and / or receive data and the transceiver 334 may include a long-range communication unit 340. In an example, the long-range communication unit 340 may be or include an LPWAN communication unit configured to communicate via one or more LPWAN protocols. In another example, the long-range communication unit 340 may be a LoRaWAN unit that is coupled to an antenna 342 to transmit and / or receive data. Thus, the power tool 302, via the wireless communication module 328, may be capable of communicating over different wireless communication protocols (e.g., BLE and / or LoRaWAN) at the same time and / or at different times. In an example, an LPWAN (Low-Power Wide Area Network) communication unit may be or56WBD (US) 4911-1825-7051include a Wi-SUN communication unit, an NB-ToT communication unit, an LTE-Mesh communication unit, a Sigfox communication unit, a Wifi-HaLow communication unit, etc.

[0241] The wireless communication module 328 may include a global navigation satellite system (GNSS) unit 344. The GNSS unit 344 may be configured to provide positional information (e.g., a latitude and a longitude) of the power tool 302. In an example, the GNSS unit 344 may be or include a global positioning system (GPS) unit, a global navigation satellite system (GLONASS) unit, a BeiDou navigation satellite system (BDS) unit, and / or a Galileo unit.

[0242] The wireless communication module 328 may include a cellular modem 346. The cellular modem 346 may allow for a subscriber identity module (SIM) card to be connected to the power tool 302. The cellular modem 346 may enable the power tool 302 to communicate (e.g., transmit and / or receive) over a cellular network. In an example, the cellular network may be or include a Long Term Evolution (LTE®) network, a fifth generation new radio (5G NR®) network, and / or another network, such as a sixth generation (6G) cellular network.

[0243] The wireless communication module 328 may include a sensor 348. In an example, the sensor 348 may be or include a location sensor, an accelerometer, a gyroscope, a magnetometer, and / or a pressure sensor. The sensor 348 may generate data that may be used by the wireless communication module 328 for various purposes.

[0244] The wireless communication module 328 may include a secondary power source 350. In some aspects, the secondary power source 350 may power the wireless communication module 328 when the power tool 302 is idle (i.e., when the power tool 302 is in an idle mode). In an example, the secondary power source 350 may be or include a coin cell (including a rechargeable or a non-rechargeable coin cell, and a serviceable or a non-serviceable coin cell), a capacitor, an accumulator, etc. In some aspects, when the power tool 302 is not idle (e.g., when the power tool57WBD (US) 4911-1825-7051302 is in active mode), a battery pack (not depicted in FIG. 3) may power the wireless communication module 328. The wireless communication module 328 may be configured to transmit and / or receive data to other devices, such as other power tools and central devices (e.g., gateways, user devices, etc.). In some aspects, the wireless communication module 328 may be configured to transmit and / or receive data from the TVth asset 104, the TVth peripheral device 108, the first central device 114, and / or the A / th central device 126.

[0245] In some aspects, the motor controller 316 may remain powered by the battery pack for a period of time (e.g., 20 seconds) after the last trigger is pulled by a user and, in a separate scenario, until a fault condition occurs. After the period of time elapses, the motor controller 316 and the wireless controller 330 may be configured to perform a shutdown procedure. The shutdown procedure may include the motor controller 316 transmitting data saved in the local memory 322 to the wireless controller 330. The shutdown procedure may also include the wireless controller 330 writing the data to the memory 332. The battery pack, which may be designated as a primary power source, may power the wireless communication module 328 in the period between a last trigger pull in a sequence and before a shutdown procedure, while the secondary power source 350 may power the wireless communication module 328 at all other times, including when the power tool 302 is idle. The power tool 302 may include a housing 307 that houses the various components (e.g., the motor 304, the wireless communication module 328, etc.) of the power tool 302.

[0246] FIG. 4 is a block diagram 400 that illustrates an example of a power tool 402 that communicates data via wireless communication network(s) in accordance with some aspects of the present disclosure. In an example, the power tool 402 may be, may include, and / or may be associated with the first asset 102 and / or the first peripheral device 106. The power tool 402 may include the motor 304, the position sensors 306, the motor control unit 308, the power module 310,58WBD (US) 4911-1825-7051the control module 312, the power switch circuit 314, the motor controller 316, the gate driver 318, the power supply regulator 320, the local memory 322, the trigger 324, and / or the tool element 326 as described above in the description of FIG. 3.

[0247] The power tool 402 may include a wireless communication module 428. The wireless communication module 428 may be connected to the motor controller 316. The wireless communication module 428 may be configured to wirelessly communicate various information to and / or from the motor controller 316. The wireless communication module 428 may include a wireless controller 430, memory 432, a first transceiver 434, and a second transceiver 435.

[0248] In some aspects, the first transceiver 434 may include a BLE unit 436 that is coupled to an antenna 438 to transmit and / or receive data and the second transceiver 435 may include a long-range communication unit 440 that is coupled to an antenna 442 to transmit and / or receive data. The long-range communication unit 440 may be or include the long-range communication unit 340. Thus, the power tool 402 may be capable of communicating over different wireless communication protocols (e.g., via the first transceiver 434 and the second transceiver 435) at the same time and / or at different times.

[0249] The wireless communication module 428 may include a GNSS unit 444. The GNSS unit 444 may be configured to provide positional information (e g., a latitude and a longitude) of the power tool 402. In an example, the GNSS unit 444 may be or include GPS unit, a GLONASS unit, a BDS unit, and / or a Galileo unit.

[0250] The wireless communication module 428 may include a cellular modem 446. The cellular modem 446 may allow for a SIM card to be connected to the power tool 402. The cellular modem 446 may enable the power tool 402 to communicate (e.g., transmit and / or receive) over a cellular59WBD (US) 4911-1825-7051network. In an example, the cellular network may be or include an LTE® network, a 5G NR® network, and / or another network, such as a sixth generation (6G) cellular network.

[0251] The wireless communication module 428 may include a sensor 448. In an example, the sensor 448 may be or include a location sensor, an accelerometer, a gyroscope, a magnetometer, and / or a pressure sensor. The sensor 448 may generate data that may be used by the wireless communication module 428 for various purposes. The power tool 402 may include a housing 307 that houses the various components (e.g., the motor 304, the wireless communication module 428, etc.) of the power tool 402.

[0252] The wireless communication module 428 may include a secondary power source 450. In some aspects, the secondary power source 450 may power the wireless communication module 428 when the power tool 402 is idle (i.e., when the power tool 402 is in an idle mode). In an example, the secondary power source 450 may be or include a coin cell (including a rechargeable or a non-rechargeable coin cell, and a serviceable or a non-serviceable coin cell), a capacitor, an accumulator, etc. In some aspects, when the power tool 402 is not idle (e.g., when the power tool 402 is in active mode), a battery pack (not depicted in FIG. 4) may power the wireless communication module 428. The wireless communication module 428 may be configured to transmit and / or receive data to other devices, such as other power tools and central devices (e.g., gateways, user devices, etc.). In some aspects, the wireless communication module 428 may be configured to transmit and / or receive data from the Vth asset 104, the TVth peripheral device 108, the first central device 114, and / or the A / th central device 126.

[0253] In some aspects, the motor controller 316 may remain powered by the battery pack for a period of time (e.g., 20 seconds) after the last trigger is pulled by a user and, in a separate scenario, until a fault condition occurs. After the period of time elapses, the motor controller 316 and the60WBD (US) 4911-1825-7051wireless controller 430 may be configured to perform a shutdown procedure. The shutdown procedure may include the motor controller 316 transmitting data saved in the local memory 322 to the wireless controller 430. The shutdown procedure may also include the wireless controller 430 writing the data to the memory 432. The battery pack, which may be designated as a primary power source, may power the wireless communication module 428 in the period between a last trigger pull in a sequence and before a shutdown procedure, while the secondary power source 450 may power the wireless communication module 428 at all other times, including when the power tool 402 is idle.

[0254] In some examples, the wireless controller 430 may, using the BLE unit 336 / 436, transmit a first periodic advertisement signal to a central device (e.g., the first central device 114) such as a gateway. The advertisement signal may include information identifying a wireless communication protocol supported by the power tool 402 and associated data, information related to a manufacturer or owner of an asset (e.g., the power tool 402), information associated with a wireless communication device (e.g., the wireless communication module 428 or a portion thereof) including a unique identifier and status information, etc. In some examples, the advertisement signal may further include operational data related to the asset (e.g., the power tool 402 and / or a battery of the power tool 402). In some aspects, the advertising signals may include only battery data (e.g., a pack temperature, a time in discharge, a runtime, etc.), tool data (e.g., tool temperature, trigger pull events, load data, fault information, etc.), or a portion of each. An example of a message format of the first advertising signal for a power tool is shown in Table 1 below.ADVERTISEMENT SIGNAL (TOOL)Portion CONTENTDATA LENGTHProtocol Header DATA LOADDATA TYPE61WBD (US) 4911-1825-7051COMPANY IDUNIQUE IDENTIFIER (MAC ADDRESS / SERIAL NUMBER) WIRELESS BLE MODULE / CELL TEMPERATUREBLE STATUS INFORMATION PRODUCT TYPE IDENTIFICATION TOOL STATUS TOTAL TRIGGER PULLS TOTAL RUNTIMEAdvertisement TOTAL TIME SPENT IN VARIABLE SPEED MODEData TOTAL TIME SPENT IN LED ONLY MODELAST SHUTDOWN STATUS 1LAST SHUTDOWN STATUS N TIME SPENT IN PACK TYPE TOTAL TIME SPENT IN MODE / OPERATING STATE CURRENT MODE / OPERATING STATECOIN CELL CHARGE STATUSSTOCK KEEPING UNIT (SKU) SPECIFIC DATATABLE 1 - An Example Advertising Message Format in Power Tool

[0255] By way of example only, the data fields in Table 1 may represent certain types of power tool operating data. For example, the “wireless BLE module / cell temperature” field may represent broadly a category of fields that list a set of temperatures of the wireless communication module 428. The “wireless BLE module / cell temperature” field may include a temperature at a most recent time the signal was generated, temperature values of each thermistor cell, and / or a temperature based on a worst-case location in the power tool 402. In some aspects, the advertisement signal may provide more granular information that subdivides the aforementioned data fields separately. The “BLE status information” field may represent broadly a category of fields that lists status information about the wireless communication module 428. For example, these fields may include status about flash memory of the power tool 402 indicating how full the memory is, which may also include a data load status indicator. The “BLE status information” field may also include strength of signal information to a closest gateway of the power tool 402. The “BLE status 62WBD (US) 4911-1825-7051information” field may also include status indicators that can allow for error codes for any subcomponents to explain their status. The “product type identification” field may represent what type of tool the advertisement message comes from. There may be multiple categories of types of tools, each designated with some code or value. The “tool status” field may provide codes or values of how the tool is functioning at present, a shutdown status of previous operation (i.e., whether the shutdown was normal or due to a fault condition), if there are any error codes, etc. The “total trigger pulls” field may represent a monotonically increasing counter of a total number of trigger pulls, including counting any partial, full, or variable trigger pulls, assuming the tool is capable of such operations. The “total runtime” field may similarly represent a monotonically increasing counter of how long the power tool 402 has been performing active actions, in some time unit such as seconds. For some power tools, there may be a “total time spent in variable speed mode” for tools that allows for operation in variable speeds, say by responding to a degree of how much a trigger of the power tool 402 is pulled. Similarly, for some power tools, there may be a “total time spend in LED only mode” for tools that allow for a trigger to turn on a work light only, say with just a minimal pull of the trigger. The LED light mode allows the tool to act as a flashlight. The “last shutdown status 1” may indicate a last status of the power tool 402 during its last shutdown procedure. The “last shutdown status 1” may include just a code or value that has a specific meaning that can be referred to in the tool’s manual, for example. There may be multiple fields of these shutdown statuses, on down to the “last shutdown status ‘N’” for the status of when the tool shutdown for the Nth to last time. This field may be a list of the last N shutdown conditions that have occurred, and the list may be updated anytime a new shutdown condition occurs. For example, “last shutdown status 1” may indicate a kickback condition, and “shutdown status 2” may indicate a locked rotor condition. When a new condition (e.g., over-temperature) occurs, the63WBD (US) 4911-1825-7051previous two shutdown conditions move respectively to shutdown statuses 2 and 3, and “shutdown status 1” may be overwritten to indicate the newly detected shutdown condition. The “time spent in pack type” field may provide a broad category of an array of fields, where each field lists the amount of time the tool is in different packs. For example, there may be a IP pack, a 2P pack, and so on, so each pack type may be listed in this array and each field may represent how much time the tool is in that particular pack type. Similarly, the “total time spent in mode / operating state” may represent a broad category of an array of fields about each mode or an operating state that the tool could be used in. The “current mode / operating state” may represent a field for a single code or value to reveal what mode or state the tool is in at the time that advertising signal was generated.

[0256] The “coin cell charge status” signal may be a binary value indicating when a state of charge and / or the voltage level of the coin cell is below a threshold. In an example, the “coin cell charge status” may be a two-bit signal that can additionally indicate whether the coin cell voltage has been or has not been read.

[0257] Table 2 below shows an example message format of an advertising indicator signal sent from a battery pack.ADVERTISEMENT SIGNAL (BATTERY PACK)Portion CONTENTDATA LENGTHProtocol Header DATA LOADDATA TYPE COMPANY ID UNIQUE IDENTIFIER (MAC ADDRESS / SERIAL NUMBER) WIRELESS BLE MODULE / CELL TEMPERATURE Advertisement BLE STATUS INFORMATIONData PRODUCT TYPE IDENTIFICATIONSTACK VOLTAGE PACK STATUS INFORMATIONHOTPACK COUNT64WBD (US) 4911-1825-7051COLDPACK COUNTFIELD-EFFECT TRANSISTOR (FET) FAULT COUNTHOT PACK CHARGER COUNT COLD PACK CHARGER COUNT PACK STATE OF CHARGE UNDER- VOLTAGE FAULT COUNTOVER-VOLTAGE FAULT COUNTOVER-CURRENT PROTECTION (OCP) FAULT COUNTTOTAL TIME IN TOOLSTOCK KEEPING UNIT (SKU) SPECIFIC DATA (PACK)TABLE 2 - Example Message Format of Advertising Signal from Battery Pack

[0258] The advertisement message format may include advertisement data relating to operation and / or performance of a battery pack (e.g., a battery pack that powers the power tool 302 and / or the power tool 402). Fields such as the company ID, unique identifier, wireless BLE module / cell temperature, BLE status information, and product type identification, may be similar to those described with reference to the tool advertisement signal above. Battery-specific advertisement data are described here. The “stack voltage” may represent a voltage of the battery pack at measured at a given number of battery cells. For example, in a battery pack including five cells in series, the stack voltage may represent the voltage of three of the cells. The “pack status information” field may provide a value or code of the status of the battery pack at the time the advertisement signal was generated. The “hotpack count” may represent the number of times the battery pack’s temperature exceeded some predetermined threshold. The temperature measurement may be based on one or more temperature sensors located at particular places in the battery pack, such as at each cell or at the location that is typically the hottest region in the battery. This field may therefore be an array of counts, one field for each location that measures temperature. Similarly, the “coldpack count” may represent the number of times the battery pack’s temperature fell below a different predetermined threshold, and may be an array of values similar65WBD (US) 4911-1825-7051to what is described for the hotpack count. The “FET fault count” may represent the number of faults of the FET in the battery pack. The “hot pack charger count” and “cold pack charger” count may represent the number of times the battery pack registered as too hot or too cold, respectively, when the battery pack was charging. These fields may be an array of values, similar to what is described above. The “pack state of charge” may represent the current state of charge of the battery pack at the time of the communication. The “Under- Voltage fault count” may represent a counter of the number of undervoltage occurrences, while the “Over-Voltage fault count” may represent a counter of the number of overvoltage occurrences. The “Over-Current Protection fault count” may represent the number of over current protection events that have occurred. The “total time in tool” is the amount of time, say in seconds, that the battery pack has been in the current tool or in other cases may be the total time that battery pack has been in all tools it has connected to. In some examples, the wireless controller 430 may, using the long-range communication unit 340 / 440, transmit a second periodic advertisement signal to a central device such as a gateway. The second period advertisement may include all or a subset of the data fields discussed above.

[0259] In an embodiment, depending on the range of the long-range communication unit 440 and / or its distance to a gateway, the wireless controller 430 may limit the number of fields included in the second periodic advertisement signal to only a subset of the data fields, where the number of fields in the subset is set by the wireless controller 430 as a function of the range of distance to the gateway. For example, the wireless controller 430 of the power tool 402 may set the number of fields to a subset of fields of higher priority and / or important (e g., status information, product type ID, tool status, last shutdown status 1 through N, and coin cell charge status) and omit other data fields (e.g., total trigger pulls, total runtime, total time spent in variable speed mode, etc.) from the second advertisement signal. Similarly, the wireless controller 430 of a battery pack may66WBD (US) 4911-1825-7051set the number of fields to a subset of fields of higher priority and / or important (e.g., stack voltage, pack state of charge, various fault counts, etc.) and omit other data fields (e.g., total time in tool, hot pack count, cold pack count, etc.) from the second advertisement signal.

[0260] In an embodiment, the wireless controller 430 may divide the number of data fields into multiple groups and transmit the second advertisement signal with one group of data fields at a time. For example, the wireless controller 430 of the power tool may transmit an initial second advertisement signal including a first group of data fields (e.g., including product type ID, tool status, total trigger pulls, total runtime, and total time spent in variable speed mode), transmit a subsequent second advertisement signal including a second group of data fields (e.g., including last shutdown status 1 through N), and yet another second advertisement signal including a third group of data fields (e.g., including total time spent in pack type, current mode, etc.). Similarly, the wireless controller 430 of the battery pack may transmit an initial second advertisement signal including a first group of data fields (e.g., product type ID, stack voltage, and pack status information), transmit a subsequent second advertisement signal including a second group of data fields (e.g., including hot pack count, cold pack count, FET fault count, hot pack charger count, and cold pack charger count), and yet another second advertisement signal including a third group of data fields (e.g., including under-voltage fault count, over-voltage fault count, over-current protection fault count, etc.).

[0261] FIG. 5 is a block diagram 500 that illustrates an example of a gateway 502 that communicates data about a power tool via wireless communication network(s) in accordance with some aspects of the present disclosure. The gateway 502 may be configured to interface with a power tool (e.g., the first asset 102, the power tool 302, the power tool 402, etc.). The gateway 502 may provide a wired connection and / or a wireless connection to a power tool and provide the67WBD (US) 4911-1825-7051power tool with a communication link between the power tool and a backend server (e.g., the backend server 116). The gateway 502 may allow a power tool to offload data that may be processed by the backend server. In an example, the gateway 502 may be or include a central device (e.g., the first central device 114).

[0262] The gateway 502 may include a gateway controller 504. The gateway controller 504 may include circuitry and processing for controlling operation of the gateway 502 as described herein. The gateway 502 may include a BLE transceiver 506 and a LoRaWAN transceiver 508. The BLE transceiver 506 may be configured to transmit and / or receive Bluetooth® signals to and / or from power tools (e.g., the first asset 102, the first peripheral device 106, the power tool 302, the power tool 402, etc ). The LoRaWAN transceiver 508 may be configured to transmit and / or receive LoRaWAN ® signals to and / or from power tools (e.g., the first asset 102, the first peripheral device 106, the power tool 302, the power tool 402, etc.). Although the BLE transceiver 506 and the LoRaWAN transceiver 508 are depicted in FIG. 5 as separate transceivers, in some aspects, the BLE transceiver 506 and the LoRaWAN transceiver 508 may be a single transceiver.

[0263] The gateway 502 may include a local area network (LAN) connector 510. The LAN connector 510 may provide a wired data connection to the gateway 502, such as to a charging station to a power tool that is also capable of transferring data from the power tool (e.g., the power tool 302, the power tool 402, etc.) while the power tool is charging. The LAN connector 510 may also provide a wired connection to a cloud network and ultimately to a backend server (e.g., the backend server 116).

[0264] The gateway 502 may include a cellular modem 512. The cellular modem 512 may provide cellular transmission capabilities, in some cases to a power tool with such capabilities and / or to a68WBD (US) 4911-1825-7051backend server. The gateway 502 may include a power supply 514 that provides power to the gateway 502.

[0265] The gateway 502 may include memory 516. The gateway 502 may store data received from a power tool, data received from another gateway, and / or data from a backend server (e.g., the backend server 116) in the memory 516.

[0266] In a construction site, gateway devices (e.g., the gateway 502) may be placed in various locations to detect advertisement signals broadcasted by various powered devices such as power tools and / or battery packs. A mobile phone including an appropriate mobile application may similarly act as a gateway and may be configured to detect advertisement signals broadcasted by various powered devices. Thus, a gateway device or a gateway may include a physical gateway device or a mobile app configured as a gateway.

[0267] Although gateway 502 is illustrated as including a BLE transceiver 506 and a LoRaWAN transceiver 508, in some examples, different BLE gateways and LoRaWAN gateways may be distributed through a jobsite. In an example, the BLE gateways and LoRaWAN gateways may be in communication with each other so they can coordinate their communication to individual assets. In some aspects, the LoRaWAN transceiver 508 may be or include a long-range communication unit, such as the long-range communication unit 340 and / or the long-range communication unit 440 described above.

[0268] FIG. 6 is a diagram 600 illustrating an example of a battery pack 602 in accordance with some aspects of the present disclosure. The battery pack 602 includes a housing 604 that houses the battery pack 602. The battery pack 602 includes a battery management controller 606 and a plurality of battery cells 608. The battery management controller 606 may control discharge of the plurality of battery cells 608. The battery management controller 606 may also be configured69WBD (US) 4911-1825-7051to detect a set of operational data of the battery pack 602. The set of operational data may include some or all of the information listed in Table 2 above. The battery pack 602 may include a thermistor 610 coupled to the battery management controller 606 that is configured to detect a temperature of the battery pack 602. The battery pack 602 may include a wireless communication controller 612 and an antenna 614 that enable the battery pack 602 to communicate wirelessly. The wireless communication controller 612 may be communicatively coupled to the battery management controller 606. In an example, the wireless communication controller 612 and the antenna 614 may enable the battery pack 602 to communicate over BLE. The battery pack 602 may include first memory 616. The battery management controller 606 and / or the wireless communication controller 612 may read and / or write data (e.g., some or all of the information listed in Table 2 above) from / to the first memory 616. The battery management controller 606 may be capable of communication with a power tool (e.g., the power tool 302, the power tool 402). For example, the battery management controller 606 may communicate with the motor control unit 308.

[0269] The battery pack 602 may include second memory 618. The battery management controller 606 may read and / or write data from / to the second memory 618. The battery pack 602 may further include an IMU 620 and / or a GNSS module 622.

[0270] FIG. 7 is a block diagram 700 that illustrates an example of the user device 120 in accordance with some aspects of the present disclosure. The user device 120 may include a processor 702 and memory 704. The memory 704 may store asset management instructions 706 that, when executed by the processor 702, cause the processor 702 to implement functionality pertaining to asset management. In some aspects, the asset management instructions 706 that, when executed by the processor 702, cause the processor 702 to implement functionality pertaining70WBD (US) 4911-1825-7051to asset and audit tracking as described herein. In some aspects, the asset management instructions 706 may be referred to as a client-side site manager.

[0271] The user device 120 may include input components 708 that enable the user device 120 to receive input from a user. In an example, the input components 708 may be or include a mouse, a keyboard, a trackpad, a touchscreen display, a scroll wheel, a microphone, etc. In some aspects, the input components 708 may be or include a camera 714, an infrared (IR) scanner 716, and / or a near field communication (NFC) module 718.

[0272] The user device 120 may further include or be associated with a display 710. In some aspects, the display 710 may be a touchscreen display. The user device 120 may present a GUI 712 on the display. In some aspects, the GUI 712 may depict asset onboarding information 720 (described in greater detail below) associated with mass onboarding of assets. In some aspects, the GUI 712 may depict geolocation-asset information 722 (described in greater detail below) associated with tracking assets on a jobsite including gateways associated with different organizations. In some aspects, the GUI 712 may depict emission information 724 for assets (described in greater detail below) powered by electricity. In some aspects, the GUI 712 may depict information pertaining to asset statuses 728 and / or information pertaining to audit statuses 730. In an example, the information pertaining to the asset statuses 728 may include or be associated with the first asset status 214 and / or the TVth asset status 216. In an example, the information pertaining to the audit statuses 730 may include or be associated with the first audit status 220 and / or the Nth audit status 222.

[0273] The user device 120 may include a wireless communication device 726 that enables the user device 120 to communicate with other devices (e.g., servers, gateways, peripheral devices associated with tools, power tools, etc ). In an example, the wireless communication device 72671WBD (US) 4911-1825-7051may be or include a BLE device (e.g., similar or identical to the BLE unit 336 and / or the BLE unit 436) and / or a long range wireless communication device (e.g., similar to the long-range communication unit 440).

[0274] FIG. 8 is a diagram 800 that illustrates a top-down view of an example of jobsites in accordance with some aspects of the present disclosure. The diagram 800 depicts a first jobsite 802 and a second jobsite 804. In an example, the first jobsite 802 may be the first jobsite 212 and the second jobsite 804 may be the second jobsite 226. In an example, the backend server 116 has generated first assignments (e.g., the first assignments 210) for the first jobsite 212 and second assignments (e.g., the second assignments 224) for the second jobsite 804 in a manner similar to that described above. In some examples, the first jobsite 802 and the second jobsite 804 may be associated with the same user account (e.g., the same owner and / or operator), or with different user accounts.

[0275] In the example depicted in FIG. 8, a first central device (CD) 806, a second CD 808, a third CD 810, a first asset (AS) 812, a second AS 814, and a third AS 816 are located in the first jobsite 802. Furthermore, in the example depicted in FIG. 8, a fourth CD 818 and a fourth AS 820 are located in the second jobsite 804. Each of the first AS 812, the second AS 814, the third AS 816, and the fourth AS 4 may include a peripheral device (not depicted in FIG. 8). The first CD 806, the second CD 808, the third CD 810, and the fourth CD 818 may be associated with a first sensing range (SR) 822, a second SR 824, a third SR 826, and a fourth SR 828, respectively. In an example, the first AS 812 may be or include the power tool 302 and / or the power tool 402.

[0276] A central device (e.g., the first CD 806, the second CD 808, the third CD 810, and the fourth CD 818) may also be referred to as a gateway. Different types of gateways may be used on a jobsite. One type of gateway is a stationary first party gateway. In an example, the gateway 50272WBD (US) 4911-1825-7051may be a stationary first party gateway. A stationary first party gateway may refer to a device for asset tracking associated with (e.g., manufactured by) an organization (e.g., a construction tool company) associated with the backend server 116 and that is disposed at a fixed location on a jobsite. A stationary first party gateway may be onboarded by a user (e.g., an enterprise user) and associated with a jobsite via an assignment maintained by the backend server 116. The assignment may include an indication of a location of the stationary first party gateway on the jobsite. When a stationary first party gateway detects an asset (e.g., via an advertisement signal emitted by the asset and received by the stationary first party gateway), the stationary first party gateway may communicate the detection to the backend server 116. Since the backend server 116 stores the location of the stationary first party gateway, the backend server 116 may determine an approximate location of the asset based on the detection of the asset by the stationary first party gateway. Furthermore, the asset and the stationary first party gateway may both be associated with a user account. As such, the backend server 116 may determine whether the asset is in a correct location based on the detection of the asset by the stationary first party gateway.

[0277] Another type of gateway may be a mobile first party gateway. A mobile first party gateway may refer to a device for asset tracking associated with an organization associated with the backend server 116 that moves around a jobsite. For example, a mobile first party gateway may move around a jobsite in a truck and / or a contractor vehicle. A mobile first party gateway may be assigned to a mobile assignment maintained by the backend server 116. An asset (e.g., a tool) may also be assigned to the mobile assignment. The mobile first party gateway may be equipped with a GNSS module. When the mobile first party gateway detects the asset, the mobile first party gateway may transmit a location (e.g., GPS coordinates) of the mobile first party gateway and an identifier for the asset to the backend server 116. The backend server 116 may then compare the73WBD (US) 4911-1825-7051location of the mobile first party gateway to a geofence boundary associated with a jobsite (e.g., in the mobile assignment). The backend server 116 may determine whether the asset is in a correct location based on the comparison. For instance, if the asset is within the geofence boundary, the asset may be in the correct location and if the asset is not within the geofence boundary, the asset may not be in the correct location.

[0278] Another type of gateway may be a third party gateway. A third party gateway may refer to a device for asset tracking that is not associated with the backend server 116. For instance, the backend server 116 may be associated with a first organization (e.g., a first company that manufactures tools) and the third party gateway may be associated with a second organization (e.g., a second company that manufactures tools), where the first organization is different from the second organization. In an example, in a large construction site (i.e., a large jobsite), there may be different types of construction tools and / or construction machinery that are used to complete a construction job, such as earth moving equipment, lifting equipment, and / or power tools. In an example, a first portion of the construction tools and / or the construction machinery may include and / or be associated with stationary first party gateways and / or mobile first party gateways, and a second portion of the construction tools and / or the construction machinery may include and / or be associated with third party gateways. In some aspects, a third party gateway may be a cellular gateway that is incorporated into a construction machine. A third party gateway may be a stationary third party gateway or a mobile third party gateway. As will be described in greater detail below, in some aspects described herein, a third party gateway may detect an advertisement signal emitted by an asset associated with an assignment maintained by the backend server 116. The advertisement signal may include an identifier for the asset and a unique company identifier associated with the first organization. The third party gateway may transmit the identifier for the74WBD (US) 4911-1825-7051asset and the unique company identifier to a server associated with the second organization. The server may then transmit the identifier for the asset and the unique company identifier (and optionally a location of the third party gateway) to the backend server 116 via an API exposed by the backend server 116 to the server. The backend server 116 may receive the identifier for the asset and the unique company identifier (and optionally the location of the third party gateway) and update an asset status of the asset based thereon.

[0279] Another type of gateway may be a public gateway. A public gateway may refer to a device associated with a crowdsourced network. The public gateway may not be associated with an organization that manufactures construction devices. A public gateway may detect an advertisement signal emitted by an asset associated with an assignment maintained by the backend server 116. The public gateway may then transmit a location of the asset for the backend server 116, either through a direct transmission of the location of the asset to the backend server 116 or by transmitting the location of the asset to a cloud server associated with the crowdsourced network which then forwards the location of the asset to the backend server 116.

[0280] FIG. 9 is a communication flow diagram 900 illustrating example communications between construction assets 902, a gateway 904, the backend server 116, and the user device 120 for mass onboarding of construction assets in accordance with some aspects of the present disclosure. In an example, the construction assets 902 may be or include the plurality of assets 102-104. In an example, the construction assets 902 may include power tools, such as the power tool 302 and / or the power tool 402, and / or battery packs, such as the battery pack 602. In an example, the gateway 904 may be or include the first central device 114 and / or the gateway 502. In some aspects, the gateway 904 and the user device 120 may be the same device (e.g., a smartphone). In some aspects, the gateway 904 and the user device 120 are different devices (e.g.,75WBD (US) 4911-1825-7051the gateway 904 may be the gateway 502 and the user device 120 may be a smartphone). In an example, the gateway 904 has previously been added to a user account (e.g., the first user account 208) maintained by the backend server 116.

[0281] At 906, each of the construction assets 902 may emit advertisement signals (e.g., via the wireless communication module 328 and / or the wireless communication module 428). In an example, the advertisement signals may be or include a Bluetooth® Low Energy (BLE) signal. In an example, the advertisement signals may be in a format such as the formats described above with respect to Table 1 and / or Table 2. For example, an advertisement signal in the advertisement signals may include the information described above in Table 1 and / or Table 2. In an example, each advertisement signal may include an identifier for a construction asset. In some aspects, at least some of the construction assets 902 may emit the advertisement signals based on power provided by a coin cell battery. In some aspects, at least some of the construction assets 902 may emit the advertisement signals when a battery pack (e.g., the battery pack 602) is inserted into a power tool (e g., the power tool 302, the power tool 402, etc.). In an example, the construction assets 902 may emit the advertisement signals periodically.

[0282] In some aspects, at 908, the user device 120 may transmit (and the gateway 904 may receive) a command to the gateway 904, where the command indicates that the gateway 904 is to perform a scan (e.g., a BLE scan). For example, the user device 120 may receive input from a user which causes the user device 120 to transmit the command. In some aspects, the command may include and / or be associated with an identifier for a user account (e.g., the first user account 208) maintained by the backend server 116 and associated with a user of the user device 120.

[0283] At 910, the gateway 904 may perform a scan (e.g., based on the command received at 908). In an example, performing the scan may include receiving the advertisement signals transmitted76WBD (US) 4911-1825-7051by the construction assets 902 via a wireless controller and / or a transceiver of the gateway 904. In some aspects, the gateway 904 may perform the scan for a period of time (e.g., several seconds, several minutes, etc.).

[0284] At 912, the gateway 904 may obtain identifiers for the construction assets based on the scan. For example, each of the advertisement signal may include a unique identifier (e.g., a MAC address, a serial number, a barcode, an International Mobile Equipment Identity (IMEI), an Integrated Circuit Card Identification (ICCID), a Mobile Equipment Identifier (MEID), a vehicle identification number (VIN), etc.) for a construction asset in the construction assets 902, and the gateway 904 may obtain the unique identifier from each advertisement signal. Obtaining the identifiers for the construction assets may be based on a range (i.e., a scanning range) of the gateway 904.

[0285] At 914, the gateway 904 may transmit (and the backend server 116 may receive) the identifiers for the construction assets and an identifier for the user account associated with the user of the user device 120.

[0286] At 916, the backend server 116 may determine that one or more construction assets in the construction assets 902 are not associated with the user account based on the identifiers for the construction assets and the identifier for the user account. For example, the backend server 116 may identify the user account based on the identifier for the user account. The backend server 116 may execute a search over data (e.g., assignments) associated with the user account based on the identifiers for the construction assets 902. The search may produce search results that indicate that the one or more construction assets in the construction assets 902 are not associated with the user account. In an example, the backend server 116 may determine that a construction asset is not associated with the user account when a unique identifier for the construction asset is not included77WBD (US) 4911-1825-7051in data (e.g., assignments) associated with the user account. In some aspects, the backend server 116 may determine that each of the construction assets 902 are not associated with the user account.

[0287] In some aspects, at 918, the backend server 116 may determine that one or more construction assets in the construction assets 902 are not associated with any user accounts maintained by the backend server 116. For example, the backend server 116 may execute a search over all user accounts (e.g., the first user account 208 and the / Jth user account 230) based on the identifiers for the construction assets. The search may produce search results that indicate that the one or more construction assets in the construction assets 902 are not associated with any user accounts maintained by the backend server 116. In an example, the backend server 116 may determine that a construction asset is not associated with any user accounts when a unique identifier for the construction asset is not included in data (e.g., assignments) associated with any user account maintained by the backend server 116. In some aspects, the backend server 116 may determine that each of the construction assets 902 are not associated with any of the user accounts maintained by the backend server 116.

[0288] At 920, the backend server 116 may add the one or more construction assets to the user account based on the determination at 916 and / or the determination at 920. Adding the one or more construction assets to the user account may include associating identifiers for the one or more construction assets with the user account. For example, the backend server 116 may link the first user account 208 with the one or more construction assets. In some aspects, at 922, the backend server 116 may transmit a confirmation to the user device 120 that indicates that at least some of the construction assets 902 have been added to the user account (e.g., the first user account 208).78WBD (US) 4911-1825-7051

[0289] In some aspects, the user of the user device may wish to enter additional information pertaining to the one or more construction assets that were added to the user account. For example, the user may wish to add images of the or more construction assets to the user account and / or inventory numbers of the or more construction assets to the user account. In another example, the user may wish to add the one or more construction assets to an assignment associated with the user account. At 924, the user device 120 may transmit (and the backend server 116 may receive) a request for a GUI for entering the additional information. At 926, based on the request, the backend server 116 may transmit (and the user device 120 may receive) data that causes the GUI to be presented on a display of the user device 120. The GUI may receive the additional information (e.g., images, inventory numbers, etc.) as input from the user. At 928, the user device 120 may transmit (and the backend server 116 may receive) the additional information pertaining to the one or more construction assets that were added to the user account.

[0290] In some aspects, the backend server 116 may have access to a log of construction asset information (e.g., a manufacturing log) that includes additional information about the one or more construction assets that were added to the user account. For example, the log may include unique identifiers (e.g., MAC addresses, serial numbers) for the one or more construction assets, build dates for the one or more construction assets, etc. In such aspects, additionally or alternatively to receiving the information about the one or more construction assets at 928, at 930, the backend server 116 may execute a search over the log based on the identifiers (e.g., MAC addresses) for the one or more construction assets (received at 914) that were added to the user account. At 932, the backend server 116 may identify information about the one or more construction assets based on search results for the search.79WBD (US) 4911-1825-7051

[0291] At 934, the backend server 116 may add information pertaining to the one or more construction assets to the user account. The information may be the information received at 928 and / or the information identified at 932. Adding the information pertaining to the one or more construction assets may include associating (e.g., linking, including a reference to, etc.) the information with the identifiers for the one or more construction assets associated with the user account.

[0292] FIG. 10 is a diagram 1000 illustrating an example of mass onboarding of assets via scanning markers of the assets in accordance with some aspects of the present disclosure. The diagram 1000 depicts the user device 120 being operated by a user 1002, and the plurality of assets 102-104. In an example, the plurality of assets 102-104 may include hundreds or thousands of assets. The first asset 102 may have a first marker 1004 affixed thereto or otherwise associated therewith. The Ath asset 104 may have an Ath marker 1006 affixed thereto or otherwise associated therewith. The first marker 1004 and the Ath marker 1006 may uniquely identify the first asset 102 and the Ath asset 104, respectively. In an example, the first marker 1004 and / or the Ath marker 1006 may be a quick-response (QR) code, such as a unique serial number (USN) QR code. In another example, the first marker 1004 and / or the Ath marker 1006 may be a barcode. In a further example, the first marker 1004 and / or the Ath marker 1006 may be a radio-frequency identification (RFID) USN sticker.

[0293] The user device 120 may perform a first scan 1008 of the first marker 1004 and an Ath scan 1010 of the Ath marker 1006 using one or more of the input components 708 of the user device 120. In one example, the user device 120 may perform the first scan 1008 and the Ath scan 1010 via the camera 714. In another example, the user device 120 may perform the first scan 100880WBD (US) 4911-1825-7051and the th scan 1010 via the IR scanner 716. Tn yet another example, the user device 120 may perform the first scan 1008 and the Nth scan 1010 via the NFC module 718.

[0294] The user device 120 may obtain an identifier (ID) for the first asset 102 (i.e., a first asset ID 1012) based on the first scan 1008. The user device 120 may add the first asset ID 1012 to a staging area 1016 (e.g., a cart) in the memory 704 of the user device 120. Similarly, the user device 120 may obtain an ID for the Nth asset 104 (i.e., an Nth asset ID 1014) based on the Nth scan 1010. The user device 120 may add the Nth asset ID 1014 to the staging area 1016. The staging area 1016 may enable the user to scan each of the plurality of assets 102-104 and add each of the plurality of assets 102-104 to a user account (e.g., the first user account 208) in one transmission without having to add assets to the user account one by one.

[0295] The user device 120 may update the GUI 712 to display an indication of the first asset 102 (e.g., the first asset ID 1012, an image of the first asset 102, etc.) based on the first asset 102 being added to the staging area 1016. The user device 120 may update the GUI 712 to display an indication of the Nth asset 104 (e g., the Nth asset ID 1014, an image of the Nth asset 104, etc.) based on the Nth asset 104 being added to the staging area 1016. The GUI 712 may include fields that enable the user device 120 to receive information about the first asset 102 (i.e., first asset information 1017) as input from the user 1002 and fields that enable the user device 120 to receive information about the Nth asset 104 (i.e., Nth asset information 1018). In an example, the first asset information 1017 and / or the Nth asset information 1018 may be or include images, inventory numbers, etc.

[0296] The user device 120 may transmit asset information 1020 to the backend server 116, whereupon the backend server 116 may add the asset information 1020 to a user account (e.g., the first user account 208) associated with the user 1002. The asset information 1020 may include the81WBD (US) 4911-1825-7051first asset ID 1012, the Mh asset ID 1014, the indication of the first asset 102, the indication of the Mh asset 104, the first asset information 1017, and / or the Mh asset information 1018.

[0297] FIG. 11 is a diagram 1100 illustrating another example of mass onboarding of assets via scanning markers of the assets in accordance with some aspects of the present disclosure. The example depicted in the diagram 1100 is similar to the example depicted in the diagram 1000. However, in the diagram 1100, after performing the first scan 1008 and the Mh scan 1010 and adding the first asset ID 1012 and the Mh asset ID 1014 to the staging area 1016 as described above in the description of the diagram 1000, the user device 120 may receive input which causes the user device 120 to transmit the staging area 1016 (including the first asset ID 1012 and theMh asset ID 1014) to a second user device 1102. In an example, the user device 120 is a smartphone operated by the user 1002 and the second user device 1102 is a desktop computing device, a laptop computing device, or a tablet computing device operated by the user 1002.

[0298] The second user device 1102 may include a processor 1104 and memory 1106. In an example, the second user device 1102 may be or include the computer system 5600 (or a portion thereof). The memory 1106 may store the staging area 1016 received by the second user device 1102 from the user device 120. The second user device 1102 may display a GUI 1108 that is similar or identical to the GUI 712. The GUI 1108 may receive the first asset information 1017 and the Mh asset information 1018 as input from the user 1002 as described above. The second user device 1102 may transmit the asset information 1020 to the backend server 116, whereupon the backend server 116 may add the asset information 1020 to a user account as described above in the description of the diagram 1000.

[0299] FIG. 12 is a diagram 1200 illustrating an example of mass onboarding of assets via detecting advertisement signals of the assets in accordance with some aspects of the present82WBD (US) 4911-1825-7051disclosure. In the example depicted in the diagram 1200, the first asset 102 and / or the first peripheral device 106 emit a first advertisement signal 1202 and the TVth asset 104 and / or the / Vth peripheral device 108 emit an Afth advertisement signal 1204. The first advertisement signal 1202 may include and / or may be indicative of the first asset ID 1012 and the Vth advertisement signal 1204 may include and / or may be indicative of the Vth asset ID 1014. In an example, the first advertisement signal 1202 and / or the A'th advertisement signal 1204 may include some or all of the information described above in Table 1 and / or Table 2 above. The user device 120 may initiate a scan for advertisement signals (e.g., such as at 910 in FIG. 9) to obtain the first asset ID 1012 and the / Vth asset ID 1014. After obtaining the first asset ID 1012 and the Vth asset ID 1014, the user device 120 may transmit the first asset ID 1012 and the / Vth asset ID 1014 to the backend server 116. The backend server 116 may receive the first asset ID 1012 and the / Vth asset ID 1014 from the user device 120. The backend server 116 may add the first asset 102 and the / Vth asset 104 to the first user account 208 (e.g., such as at 920 in FIG. 9) based on the first asset ID 1012 and the Arth asset ID 1014. In an example, the first user account 208 is associated with the user 1002.

[0300] FIG. 13 is a diagram 1300 illustrating another example of mass onboarding of assets via detecting advertisement signals of the assets in accordance with some aspects of the present disclosure. The example depicted in the diagram 1300 is similar to the example depicted in the diagram 1200. However, in the diagram 1300, the user device 120 may receive input from the user 1002 which causes the user device 120 to transmit a scan command 1302 to the gateway 502. The gateway 502 may receive the scan command 1302 and perform a scan (e.g., such as at 910 in FIG. 9) based on the scan command 1302. The gateway 502 may obtain the first asset ID 1012 and the / Vth asset ID 1014 based on the scan in a manner similar to that described above in the83WBD (US) 4911-1825-7051description of the diagram 1200. The gateway 502 may transmit the first asset ID 1012 and the Mh asset ID 1014 to the backend server 116. The backend server 116 may receive the first asset ID 1012 and the Mh asset ID 1014 from the gateway 502. The backend server 116 may add the first asset 102 and the h asset 104 to the first user account 208 based on the first asset ID 1012 and the Mh asset ID 1014 in a manner similar to that described above in the description of the diagram 1200.

[0301] FIG. 14 is a diagram 1400 illustrating an example of onboarding a kit and / or a pallet of assets via a scan in accordance with some aspects of the present disclosure. In the example depicted in the diagram 1400, the first asset 102 and the Mh asset 104 are included in a kit or a pallet (referred to hereafter as a kit / pallet 1402). A kit may refer to a collection of different types of construction assets (e.g., power tools) that are packaged together. A pallet may refer to a collection of construction assets that are packaged together. A pallet may include multiple construction assets (e.g., power tools) of the same type or different types. A number of construction assets in a pallet may be greater than a number of assets in a kit. The kit / pallet marker 1404 may include and / or be indicative of an identifier for the kit / pallet 1402 (referred to hereafter as a kit / pallet ID 1406). The kit / pallet 1402 may include a kit / pallet marker 1404. In an example, the kit / pallet marker 1404 may be or include a QR code, such as a USN QR code. In another example, the kit / pallet marker 1404 may be or include a barcode. In a further example, the kit / pallet marker 1404 may be an RFID USN sticker.

[0302] The user device 120 may perform a scan 1408 of the kit / pallet marker 1404 (e.g., via the camera 714, the IR scanner 716, and / or the NFC module 718) in a manner similar to that described above in the description of the diagram 1000. The user device 120 may obtain the kit / pallet ID 1406 based on the scan 1408. The user device 120 may transmit the kit / pallet ID 1406 to the84WBD (US) 4911-1825-7051backend server 116. The backend server 116 may receive the kit / pallet ID 1406 from the user device 120.

[0303] The backend server 116 may store a kit / pallet ID lookup table 1410 in the memory 204 or other data storage (or have access to the kit / pallet ID lookup table 1410). The kit / pallet ID lookup table 1410 may map kit / pallet IDs of kits / pallets to identifiers for assets included in the kits / pallets. In some aspects, the kit / pallet ID lookup table 1410 also maps the kit / pallet IDs of the kits / pallets to other information about the assets included in the kits / pallets. The backend server 116 may obtain an identifier for the first asset 102 (e.g., the first asset ID 1012) and an identifier for the / Vth asset 104 (e.g., the / Vth asset ID 1014) by looking up an entry in the kit / pallet ID lookup table 1410 based on the kit / pallet ID 1406 received from the user device 120. In some aspects, the backend server 116 may obtain additional information about the first asset 102 and the / Vth asset 104 via the kit / pallet ID lookup table 1410. The backend server 116 may add each of the plurality of assets 102-104 to the first user account 208 based on information obtained from the kit / pallet ID lookup table 1410.

[0304] FIG. 15 is a communication flow diagram 1500 illustrating example communications between power tools 1502, the gateway 502, the backend server 116, and the user device 120 for calculating and displaying CChe emissions of the power tools 1502 in accordance with some aspects of the present disclosure. The power tools 1502 are powered by electricity (as opposed to gas or another non-renewable power source). Furthermore, the power tools 1502 may be associated with the gateway 502 (e.g., in an assignment). In an example, the power tools 1502 may be or include the power tool 302 and / or the power tool 402.

[0305] The power tools 1502 may generate and store information as the power tools 1502 operate. The information may include a runtime of each of the power tools 1502. Runtime of a power tool85WBD (US) 4911-1825-7051may represent an amount of time that the power tool was consuming power (e g., during active use). In some aspects, the information may include an amount of energy (e.g., in kilowatt-hours (kWh)) used by a power tool in the power tools 1502 if the power tool supports such functionality. In some aspects, the information may include a location (e.g., a global positioning system (GPS) coordinates or other global navigation satellite system (GNSS) coordinates) of a power tool in the power tools 1502 if the power tool supports such functionality. In some aspects, the information may include an identifier for each of the power tools 1502. In some aspects, the information may include a type (e.g., screed, vibrator, rammer, plate compactor, etc.) of each of the power tools 1502. At 1504, the power tools 1502 may transmit (and the gateway 502 may receive) the information including at least the runtime of each of the power tools 1502. In some aspects, the information may additionally include an energy (e.g., in kWh) used by the power tools 1502 (or batteries). At 1506, the gateway 502 may transmit (and the backend server 116 may receive) the information including at least the runtime of each of the power tools 1502.

[0306] At 1508, the backend server 116 may obtain an estimate of emissions of a power grid that provides power to the power tools 1502 based on a location of the power tools 1502. For example, if the information received at 1506 includes GPS coordinates of a power tool in the power tools 1502, the backend server 116 may obtain a Zone Improvement Plan (ZIP) code of the power tool based on the GPS coordinates using a GPS coordinates to ZIP code lookup table. In another example, if the information received at 1506 does not include GPS coordinates of a power tool in the power tool s 1502, the backend server 116 may determine a location of the power tools based on data stored in an assignment associated with the power tool and maintained by the backend server 116. For instance, if the assignment includes GPS coordinates, the backend server 116 may use the GPS coordinates included in the assignment and the GPS coordinates to ZIP code lookup86WBD (US) 4911-1825-7051table to determine the ZIP code. If the assignment includes an address including a ZIP code, the backend server 116 may obtain the ZIP code from the assignment. In some aspects, the GPS coordinates to ZIP code lookup table may be stored at the backend server 116 and the backend server 116 obtains the ZIP code using the GPS coordinates to ZIP code lookup table stored at the backend server 116. In some other aspects, the backend server 116 utilizes a service to obtain the ZIP code based on the GPS coordinates. The backend server 116 may provide the ZIP code for the power tools 1502 to a power profiler tool (which may be hosted either at the backend server 116 or another device) to obtain the estimate of emissions of the power grid. With more particularity, the backend server 116 may obtain a mass of CChe emitted by the power grid per megawatt hour (e.g., kg / MWh, kg / kWh) for the power grid based on the ZIP code. In some aspects, the backend server 116 may obtain the estimate of the emissions of the power grid from a governmental data source (e.g., the Environmental Protection Agency (EP A) and / or another public data source.

[0307] At 1510, the backend server 116 may calculate CCEe emissions of the power tools 1502 based on the estimate of emissions of the power grid. CO2e emissions may refer to a standard unit used to measure an overall impact of different greenhouse gases on a climate. CO2e may represent an amount of CO2 that would have the same warming effect as a given amount of another greenhouse gas, such as methane or nitrous oxide. CChe may enable the comparison and aggregation of various greenhouse gases into a single metric to enable organizations to track a total climate impact of power tools. In an example, if the information received at 1506 includes an amount of energy (e.g., in kWh) used by a power tool in the power tools 1502, the backend server 116 may multiply the amount of energy by the estimate of emissions of the power grid to obtain the CChe emissions of the power tool. In another example, if the information received at 150687WBD (US) 4911-1825-7051does not include the amount of energy used by the power tool in the power tools 1502, the backend server 116 may obtain an estimated amount of energy (e.g., in kWh per runtime) used by the power tool based on a type of the power tool. For example, the backend server 116 may look up an energy consumption (e.g., in a log of information that includes information about a particular type of power tool) of the power tool based on an identifier for the power tool, such as a stock keeping unit (SKU). The backend server 116 may multiply the estimated amount of energy by the runtime to obtain the CChe emissions of the power tool.

[0308] At 1512, the backend server 116 may calculate a volume (e.g., in gallons, in liters, etc.) of gasoline that would have been used by the power tools 1502 if the power tools were powered by gasoline. For example, the backend server 116 may have access to a log of information that includes a volume of gasoline consumed per hour by a power tool in the power tools 1502 had the power tool been powered by gasoline instead of electricity. The backend server 116 may multiply the runtime of each of the power tools 1502 by the aforementioned volume per hour to obtain the volume of gasoline.

[0309] At 1514, the backend server 116 may calculate, based on the volume calculated at 1512, CChe emissions that would have been produced by the power tools 1502 had the power tools 1502 been powered by gasoline instead of electricity. For example, the backend server 116 may multiply the volume calculated at 1512 by a CO2 emissions coefficient for finished motor gasoline to obtain a value of kg CO2. The backend server 116 may then multiple the value of kg CO2 by 12 / 44 to obtain the CChe emissions that would have been produced by the power tools 1502 had the power tools 1502 been powered by gasoline instead of electricity.

[0310] At 1516, the user device 120 may transmit (and the backend server 116 may receive) a request for a GUI that is to depict graphical information pertaining to emissions of the power tools88WBD (US) 4911-1825-70511502. At 1518, based on receiving the request, the backend server 116 may transmit (and the user device 120 may receive) data that includes the GUI. At 1520, the user device 120 may present the GUI on the display 710 of the user device 120. The GUI may include the values calculated at 1510, 1512, and / or 1514. In some aspects, the GUI includes information depicted in FIG. 16 and / or FIG. 17 (described below).

[0311] In some aspects, at 1522, the user device 120 may transmit (and the backend server 116 may receive) a request for tabular data pertaining to the emissions of the power tools 1502. In an example, the tabular data may be or include a spreadsheet that includes the values calculated at 1510, 1512, and / or 1514. In another example, the tabular data may be or include a comma-separated values (CSV) file that includes the values calculated at 1510, 1512, and / or 1514. At 1524, based on the request, the backend server 116 may transmit (and the user device 120 may receive) the tabular data.

[0312] In some aspects, the power tools 1502, the gateway 502, and the backend server 116 may perform the steps described at 1504, 1506, 1508, 1510, 1512, and 1514 at a recurring time interval. For example, the recurring time interval may be once a day, once a week, once a month, etc. Although the backend server 116 is described above as calculating CChe emissions, a volume of gasoline, and CChe emissions if the power tools 1502 were powered by gasoline instead of electricity, in some aspects, the aforementioned calculations may be performed by the user device 120.

[0313] Although the description of FIG. 15 above focuses on CChe emissions, it is to be understood that the concepts discussed herein may also be applicable to CO2 emissions and / or all greenhouse gases. Although the description of FIG. 15 above describes gasoline-based89WBD (US) 4911-1825-7051calculations, it is to be understood that the concepts described herein may also be applicable to diesel-based calculations and / or fossil fuel-based calculations.

[0314] FIG. 16 is a diagram 1600 illustrating an example of a graphical user interface (GUI) for displaying CChe emissions of the power tools in accordance with some aspects of the present disclosure. In an example, the user device 120 may present the GUI depicted in the diagram 1600 (e.g., at 1520 in FIG. 15). In an example, the GUI depicted in the diagram 1600 may be or include the GUI 712.

[0315] The GUI may include a carbon impact section 1602. The carbon impact section 1602 may include an indication of a number of assets (e.g., power tools) for which CChe emissions were calculated. The carbon impact section 1602 may include an indication of a total runtime of the assets. The total runtime of the assets may be a sum of a runtime of each of the assets. The carbon impact section 1602 may include an indication of an amount of CChe emissions of the assets (e.g., in megatons (MT)). The GUI may include a CC e emissions by assignment section 1604. The CChe emissions by assignment section 1604 may include an indication of CChe emissions for each type of assignment (e.g., jobsite, project, work truckjob box, warehouse, etc.).

[0316] The GUI may include an impact equivalent section 1606. The impact equivalent section 1606 may include an indication of a number of tons of CChe emissions of the assets. The impact equivalent section 1606 may also include an indication of a number of tons of CChe emissions that would have been emitted by the assets had the assets been powered by gas instead of electricity.

[0317] The GUI may include an emissions CChe by asset class section 1608. The emissions CChe by asset class section 1608 may indicate, for each month of a year, a total number of CChe emissions by the assets. The emissions CChe by asset class section 1608 may also indicate (e.g.,90WBD (US) 4911-1825-7051via different colors), for each month of the year, CChe emissions produced by each asset class (e.g., screed, vibrator, rammer, plate compactor, etc.).

[0318] In some aspects, the GUI may include a first selectable element 1610 and a second selectable element 1612. In such aspects, the user device 120 may present the emissions CChe by asset class section 1608 within the GUI upon a selection of the first selectable element 1610.

[0319] FIG. 17 is a diagram 1700 illustrating another example of a GUI for displaying CChe emissions of the power tools in accordance with some aspects of the present disclosure. In an example, the user device 120 may present the GUI depicted in the diagram 1700 (e.g., at 1520 in FIG. 15). In an example, the GUI depicted in the diagram 1700 may be or include the GUI 712. The GUI depicted in the diagram 1700 may include the carbon impact section 1602, CO2e emissions by assignment section 1604, and the impact equivalent section 1606, each of which are described above in the description of FIG. 16.

[0320] The GUI may also include an emissions CC e by asset class section 1702. The emissions CChe by asset class section 1702 may include an indication of a total number of CChe emissions by assets. The emissions CChe by asset class section 1702 may also include a pie chart that shows a relative contribution (e.g., via different colors) of each asset class to the total number of CO2e emissions. In some aspects, the user device 120 may present the emissions CO2e by asset class section 1702 within the GUI upon a selection of the second selectable element 1612.

[0321] FIG. 18 is a communication flow diagram 1800 illustrating example communications between a construction asset 1802, a first gateway 1804 associated with both a first organization and a vehicle 1806, a second gateway 1808 associated with a second organization (different from the first organization), the backend server 116 (associated with the first organization), a server 1810 associated with the second organization, and the user device 120 for tracking a status of the91WBD (US) 4911-1825-7051construction asset in accordance with some aspects of the present disclosure. In an example, the construction asset 1802 may be or include the first asset 102. In an example, the construction asset 1802 may be or include the power tool 302 and / or the power tool 402. In another example, the construction asset 1802 may be or include the battery pack 602. In a further example, the construction asset 1802 may be or include a wireless tag. In an example, the first gateway 1804 may be or include the gateway 502 and / or the first central device 114. In some aspects, the first organization is a first manufacturer of construction assets and the second organization is a second manufacturer of construction assets. The second gateway 1808 associated with the second organization may be referred to as a third party gateway. The server 1810 associated with the second organization may be referred to as a third party server. In some aspects, the first gateway 1804 is disposed in the vehicle 1806. In some aspects, the first gateway 1804 is part of the vehicle 1806. It is contemplated that the first organization has exposed an application programming interface (API) of the backend server 116 to the second organization such that the server 1810 is able to communicate details pertaining to construction assets (e.g., construction assets associated with the first organization) to the backend server 116.

[0322] At 1812, the backend server 116 may generate a mobile assignment. In an example, the mobile assignment may be included in the first assignments 210 associated with the first user account 208. The mobile assignment may include the first gateway 1804 and the construction asset 1802, and may indicate that the first gateway 1804 is to track a status of the construction asset 1802. The mobile assignment may also indicate that the first gateway 1804 and the construction asset 1802 are associated with a jobsite (e.g., the first jobsite 212). It is contemplated that the vehicle 1806 may travel around, within, and / or outside of the jobsite. It is also contemplated that the second gateway 1808 is located in / on the jobsite. At 1814, the backend92WBD (US) 4911-1825-7051server 116 may establish a geofence boundary for the jobsite. The geofence boundary may indicate a perimeter of an area that is considered to be the jobsite. For instance, the geofence boundary may be a set of GPS coordinates that define a closed area considered to be the jobsite.

[0323] It is contemplated that the construction asset 1802 (or a peripheral device associated with the construction asset) periodically emits an advertisement signal. The advertisement signal may include some or all of the information described above in Table 1 and / or Table 2. The first gateway 1804 may receive the advertisement signal of the construction asset 1802 and update an asset status and / or an audit status of the construction asset 1802 based thereon (not depicted in FIG. 18).

[0324] At some point during a construction job, at 1816, the first gateway 1804 may fail to detect the advertisement signal of the construction asset 1802. For example, the construction asset 1802 may be moved outside of a range (i.e., a detection range) of the first gateway 1804 in / on the vehicle 1806. The detection range may be a distance at which a wireless communication device (e.g., the BLE transceiver 506, the LoRaWAN transceiver 508, etc.) may receive wireless signals from devices. In another example, the vehicle 1806 that carries that first gateway 1804 may move away from the construction asset 1802 such that the construction asset 1802 is no longer within the detection range of the first gateway 1804. In yet another example, a wireless communication device of the first gateway 1804 may become non-operational such that the first gateway 1804 fails to detect the advertisement signal. In a further example, wireless interference from other devices located near the first gateway 1804 may cause the first gateway 1804 to fail to detect the advertisement signal.

[0325] At 1818, the second gateway 1808 may receive the advertisement signal emitted by the construction asset 1802. For example, the construction asset 1802 may be located within a detection range of the second gateway 1808. In an example, the second gateway 1808 may be93WBD (US) 4911-1825-7051configured to receive and process a portion of the advertisement signal. For example, the second gateway 1808 may be configured to interpret an identifier for the construction asset 1802 (e.g., a MAC address) included in the advertisement signal, but not other information included in the advertisement signal (e.g., a total runtime of the construction asset 1802). At 1820, the second gateway 1808 may transmit (and the server 1810 may receive) an identifier for the construction asset 1802 (i.e., a construction asset identifier). In some aspects, the second gateway 1808 may additionally transmit an indication of a location of the second gateway 1808 along with the construction asset identifier.

[0326] At 1830, the server 1810 may transmit (and the backend server 116 may receive) the construction asset identifier for the construction asset 1802 and an indication of the location of the second gateway 1808 via an API exposed by the backend server 116 to the server 1810. In some aspects, the indication of the location of the second gateway 1808 may be received by the server 1810 from the second gateway 1808. In some aspects, the indication of the location of the second gateway 1808 may be maintained by server 1810 (e.g., in an assignment-like manner).

[0327] At 1834, the backend server 116 may compare the location of construction asset 1802 (received from the server 1810) to the geofence boundary established at 1814. For instance, the backend server 116 may compare the location of the construction asset 1802 to determine if the construction asset 1802 is still located on the jobsite. At 1834, the backend server 116 may update an asset status for the construction asset 1802 based on the comparison at 1832. For instance, the backend server 116 may update the asset status to indicate that the construction asset 1802 is at a wrong location on the jobsite or at a correction location on the jobsite.94WBD (US) 4911-1825-7051

[0328] In some aspects, at 1836, the backend server 116 may transmit (and the user device 120 may receive) an indication of an updated status for the construction asset 1802. At 1838, the user device 120 may present a GUI on the display 710, where the GUI indicates the updated asset status.

[0329] In some aspects, at 1817, the backend server 116 may determine that the first gateway 1804 has failed to detect the construction asset 1802. In an example, the backend server 116 may receive a message (not depicted in FIG. 18) from the first gateway 1804 indicating that the first gateway 1804 has not detected the advertisement signal of the construction asset 1802 within an audit window. In another example, the backend server 116 may determine that the backend server 116 has not received an indication of the construction asset 1802 from the first gateway 1804 (or another gateway associated with the first organization) within an audit window for the construction asset 1802.

[0330] In some aspects, at 1822, the backend server 116 may transmit (and the server 1810 may receive) the identifier for the construction asset 1802 based on the determination at 1817. The transmitted identifier may be the same as the identifier received by the server 1810 from the second gateway 1808 at 1820. In such aspects, the server 1810 may transmit the identifier for the construction asset 1802 and the indication of the location of the construction asset 1802 based on the identifier received by the server 1810 at 1822.

[0331] Although the description of FIG. 18 describes the second gateway 1808 and the server 1810 as being associated with a second organization, other possibilities are contemplated. In some aspects, the second gateway 1808 and the server 1810 may be associated with a public crowdsourced network.

[0332] FIG. 19A is a diagram 1900A illustrating an example of a jobsite 1902 including the first gateway 1804 associated with a first organization and the second gateway 1808 associated with a95WBD (US) 4911-1825-7051second organization at a first time instance in accordance with some aspects of the present disclosure. The diagram 1900A depicts a first range 1904 (i.e., a first detection range) of the first gateway 1804 and a second range 1906 (i.e., a second detection range) of the second gateway 1808. In an example, the first range 1904 may be a range of a BLE transceiver and / or a range of a LoRaWAN transceiver. In the example depicted in the diagram 1900A, the construction asset 1802 emits an advertisement signal 1908. The advertisement signal 1908 may be or include some or all of the information in Table 1 and / or Table 2 above. As the construction asset 1802 is located within the first range 1904 of the first gateway 1804, the first gateway 1804 receives the advertisement signal 1908.

[0333] FIG. 19B is a diagram 1900B illustrating an example of the jobsite 1902 including the first gateway 1804 associated with a first organization and the second gateway 1808 associated with a second organization at a second time instance in accordance with some aspects of the present disclosure. The second time instance may occur after the first time instance. As shown in the diagram 1900B, the construction asset 1802 is no longer within the first range of the first gateway 1804 (e.g., due to movement of the construction asset 1802 and / or the vehicle 1806 carrying the first gateway 1804).

[0334] The construction asset 1802 may continue to emit the advertisement signal 1908. As the construction asset 1802 is now located within the second range 1906 of the second gateway 1808, the second gateway 1808 may receive the advertisement signal 1908 (e.g., as illustrated at 1818 in FIG. 18). The second gateway 1808 transmit an identifier for the construction asset 1802 indicated / included in the advertisement signal 1908 to the server 1810 as illustrated at 1820 in FIG. 18).96WBD (US) 4911-1825-7051

[0335] FIG. 20 is a decision flow diagram 2000 illustrating example decisions for tracking a status of an asset in accordance with some aspects of the present disclosure. In an example, the decision flow diagram 2000 may be implemented / performed by the backend server 116.

[0336] At 2002, the backend server 116 may onboard an asset (e.g., a power tool, a battery pack, etc.). At 2004, the backend server 116 may determine whether the asset is assigned to an assignment (e.g., an assignment in the first assignments 210). Upon negative determination at 2004, at 2006, the backend server 116 may set an audit status (e.g., the first audit status 220) for the asset as “unassigned.” Subsequently, at 2008, the backend server 116 may assign the asset to an assignment. After assigning the asset to the assignment, at 2010, the backend server 116 may set an audit status for the asset as “needs audit.” Upon positive determination at 2004 (i.e., the asset is assigned to an assignment), at 2010, the backend server may set an audit status for the asset as “needs audit.”

[0337] At 2012, the backend server 116 may ascertain a last seen timestamp of the asset. The last seen timestamp of the asset may be provided by a gateway associated with the asset in the assignment. At 2014, the backend server 116 may determine whether the last seen timestamp is greater than an assignment audit window associated with the assignment. Upon negative determination at 2014, the backend server 116 may return to 2012 described above. Upon positive determination at 2014, at 2016, the backend server 116 may set the audit status for the asset as “overdue.”

[0338] FIG. 21 is a decision flow diagram 2100 illustrating example decisions for tracking a status of an asset in accordance with some aspects of the present disclosure. In an example, the decision flow diagram 2100 may be implemented / performed by the backend server 116.97WBD (US) 4911-1825-7051

[0339] At 2102, the backend server 116 may obtain an indication that an asset has been detected by an application (“an app”) and / or a gateway. At 2104, the backend server 116 may determine whether the detected asset is assigned to an assignment. Upon negative determination at 2104, at 2106, the backend server 116 may set an audit status (e.g., the first audit status 220) for the asset to “unassigned.”

[0340] Upon positive determination at 2104, at 2018, the backend server 116 may determine whether the asset is assigned to the same assignment as the gateway (or whether the asset is selected by a user of the app). Upon negative determination at 2108 (i.e., the assigned is not assigned to the same assignment or the asset has not been selected by the user of the app), at 2110, the backend server 116 may set an audit status for the asset to “wrong location.” Upon positive determination at 2108 (i.e., the assigned is assigned to the same assignment as a gateway or the asset been selected by the user of the app), at 2112, the backend server 116 may set the audit status for the asset to “audited.”

[0341] FIG. 22 is a decision flow diagram 2200 illustrating example decisions for tracking a status of an asset in accordance with some aspects of the present disclosure. In an example, the decision flow diagram 2200 may be implemented / performed by the backend server 116.

[0342] At 2202, the backend server 116 may obtain an indication that an asset was detected by a third party gateway (i.e., a gateway that is not managed / under the control of the backend server 116). At 2204, the backend server 116 may determine whether the asset is assigned to an assignment. Upon negative determination at 2204 (i.e., the asset is not assigned to an assignment), the backend server 116 may set an audit status (e.g., the first audit status 220) for the asset to “unassigned.”98WBD (US) 4911-1825-7051

[0343] Upon positive determination at 2204 (i.e., the asset is assigned to an assignment), at 2206, the backend server 116 may determine whether the assignment is a home assignment or a site assignment (i.e., a fixed). Upon negative determination at 2206 (i.e., the assignment is not a home or a site assignment), at 2208, the backend server 116 may determine whether a third party gateway identifier is in a list of third party gateways for the assignment of the asset. Upon negative determination at 2208 (i.e., the third party gateway identifier is not in the list of third party gateways for the assignment of the asset), at 2210, the backend server 116 may set an audit status for the asset as “wrong location.” Upon positive determination at 2208 (i.e., the third party gateway identifier is in the list of third party gateways for the assignment of the asset), at 2212, the backend server 116 may set the audit status for the asset to “audited.”

[0344] Referring back to 2206, upon positive determination at 2206 (i.e., the assignment type is home or site), at 2214, the backend server 116 may determine whether the assignment has a location. Upon negative determination at 2214 (i.e., the assignment does not have a location), the backend server may perform the determination at 2208 as described above.

[0345] Upon positive determination at 2214 (i.e., the assignment has a location), at 2216, the backend server 116 may determine whether the asset is within an assignment boundary (i.e., a geofence). Upon positive determination at 2216 (i.e., the asset is within the assignment boundary), at 2212, the backend server 116 may set an audit status for the asset to “audited.” Upon negative determination at 2216 (i.e., the asset is not within the assignment boundary), at 2210, the backend server 116 may set an audit status for the asset as “wrong location.”

[0346] FIG. 23 is a diagram 2300 illustrating an example of a GUI for adding an assignment in accordance with some aspects of the present disclosure. In an example, the GUI depicted in the diagram 2300 may be or include the GUI 712. The GUI may include an add assignment button99WBD (US) 4911-1825-70512302 that, when selected, causes an add assignment window 2304 to be displayed. The add assignment window 2304 may include a fixed assignment selectable element 2306, that, when selected, causes a fixed assignment (e.g., in the first assignments 210) to be created and associated with a user account (e.g., the first user account 208). The add assignment window 2304 may include a mobile assignment selectable element 2308, that, when selected, causes a mobile assignment (e.g., in the first assignments 210) to be created and associated with a user account (e.g., the first user account 208). The add assignment window 2304 may include a home assignment selectable element 2310, that, when selected, causes a home assignment (e.g., in the first assignments 210) to be created and associated with a user account (e.g., the first user account 208).

[0347] FIG. 24 is a diagram 2400 illustrating an example of a GUI for adding details to a fixed assignment in accordance with some aspects of the present disclosure. In an example, the GUI depicted in the diagram 2400 may be or include the GUI 712. The user device 120 may display the GUI when the fixed assignment selectable element 2306 is selected.

[0348] The GUI may include an assignment details field 2402 that is configured to receive assignment details as input. The assignment details may include an assignment name, a job code, and / or a point of contact for the assignment. The GUI may include an assigned people field 2404 that enables a user to select individuals who are to have access to the fixed assignment referenced in the GUI.

[0349] The GUI may include a location and audit field 2406 that may receive a location of the assignment as input. The location and audit field 2406 may also display locations of gateways that can be associated with the assignment and respective coverage areas of the gateways. In some aspects, the locations of the gateways may be displayed on a map. In some aspects, the location100WBD (US) 4911-1825-7051and audit field 2406 may include a toggle bar that enables a user to set an assignment radius for the fixed assignment referenced in the GUI.

[0350] The GUI may include an audit frequency field 2408 that enables a user to set an audit frequency (e.g., monthly, daily, etc.) for assets assigned to the fixed assignment referenced in the GUI. The audit frequency field 2408 may also include an option to enable the backend server 116 to send audit report emails individuals selected in the assigned people field 2404.

[0351] FIG. 25 is a diagram 2500 illustrating another example of a GUI for adding details to a fixed assignment in accordance with some aspects of the present disclosure. In an example, the GUI depicted in the diagram 2500 may be or include the GUI 712. The GUI depicted in the diagram 2500 depicts a version of the GUI in the diagram 2400 after the assignment details field 2402, the assigned people field 2404, the location and audit field 2406, and the audit frequency field 2408 have received input including details for a fixed assignment.

[0352] The location and audit field 2406 depicted in the diagram 2500 depicts a fixed assignment 2502. In an example, the fixed assignment 2502 is included in the first assignments 210. As shown in the diagram 2500, a first gateway 2504 and a second gateway 2506 are included within the radius of the fixed assignment 2502. In an example, the first gateway 2504 and / or the second gateway 2506 may be or include the gateway 502. As depicted in the diagram 2500, coverage ranges of the first gateway 2504 and the second gateway 2506 do not encompass an entirety of the area of the fixed assignment 2502.

[0353] FIG. 26 is a diagram 2600 illustrating of a GUI for adding details to a mobile assignment in accordance with some aspects of the present disclosure. In an example, the GUI depicted in the diagram 2600 may be or include the GUI 712. The user device 120 may display the GUI when the mobile assignment selectable element 2308 is selected.101WBD (US) 4911-1825-7051

[0354] The GUI may include an assignment details field 2602 that is configured to receive assignment details as input. The assignment details may include an assignment name, a job code, and / or a point of contact for the assignment. The GUI may include an assigned people field 2604 that enables a user to select individuals who are to have access to the mobile assignment referenced in the GUI.

[0355] The GUI may include a vehicle ID and audit field 2606 that is configured to receive, as input, details pertaining to a vehicle associated with the mobile assignment referenced in the GUI. The vehicle may be a gateway itself and / or the vehicle may carry a gateway that is disposed in the vehicle. The details pertaining to the vehicle may include a vehicle identifier of the vehicle, a license plate number of the vehicle, a make of the vehicle, and / or a model of the vehicle.

[0356] The GUI may include an audit frequency field 2608 that enables a user to set an audit frequency (e.g., monthly, daily, etc.) for assets assigned to the mobile assignment referenced in the GUI. The audit frequency field 2608 may also include an option to enable the backend server 116 to send audit report emails individuals selected in the assigned people field 2604.

[0357] FIG. 27 is a communication flow diagram 2700 that illustrates example communications between the first asset 102 including the first peripheral device 106, the first central device 114, the backend server 116, and the user device 120 for asset and audit status management in accordance with some aspects of the present disclosure.

[0358] At 2702, the user device 120 may transmit assignment generation data to the backend server 116 and the backend server 116 may receive the assignment generation data. The assignment generation data may be for a construction project or other work performed on a jobsite. For example, the user device 120 may receive input that is indicative of the first assignments 210, and at 2702, the user device 120 may transmit data reflecting the input to the backend server 116.102WBD (US) 4911-1825-7051For instance, the assignment generation data may include identifiers for the plurality of assets 102-104 (e.g., identifiers for tools, medium access control (MAC) addresses for peripheral devices associated with the plurality of assets 102-104, etc.), an identifier for the first jobsite 212, an identifier for the first central device 114 (e g., a MAC address for the first central device 114), and an indication that the plurality of assets 102-104 are assigned to / linked to the first jobsite 212 and / or the first central device 114. The assignment generation data may also include the first asset status 214 and / or the Mh asset status 216.

[0359] At 2704, the backend server 116 may generate assignments based on the assignment generation data. For example, the backend server 116 may generate the first assignments 210 and / or the second assignments 224 based on the assignment generation data. Prior to, concurrently with, or subsequent to generating the assignments, the plurality of assets 102-104 and the first central device 114 may be deployed to the first jobsite 212.

[0360] At 2706, the backend server 116 may transmit an indication of the first assignments 210 to the first central device 114 and the first central device 114 may receive the indication of the first assignments 210. The backend server 116 may also transmit indication(s) of other assignments to other central devices.

[0361] At 2708, the first central device 114 may begin to monitor for signals from the plurality of assets 102-104 based on the first assignments 210. Monitoring for the signals may be based on a time period defined by the first audit frequency 218.

[0362] In an example, at 2710, the first central device 114 may detect / sense / receive the first signal 110 emitted / transmitted / broadcast by the first peripheral device 106 within the time period defined by the first audit frequency 218. In the example, at 2712, the first central device 114 may transmit the first audit status 220 to the backend server 116 based on the detection / sensing / receipt of the103WBD (US) 4911-1825-7051first signal 110 and the backend server 116 may receive the first audit status 220 from the first central device 114. In the example, the first audit status 220 may indicate that the first asset 102 has been audited (i.e., the first asset 102 is located at an expected location of the first asset 102).

[0363] In another example, at 2710, the first central device 114 may fail to detect / sense / receive the first signal 110 emitted / transmitted / broadcast by the first peripheral device 106 within the time period defined by the first audit frequency 218. In the example, at 2712, the first central device 114 may transmit the first audit status 220 to the backend server 116 based on failing to detect / sense / receive the first signal 110 and the backend server 116 may receive the first audit status 220 from the first central device 114. In the example, the first audit status 220 may indicate that the first asset 102 is overdue for an audit.

[0364] In another example, at 2710, the first central device 114 may fail to detect / sense / receive the first signal 110 emitted / transmitted / broadcast by the first peripheral device 106, but the time period defined by the first audit frequency 218 may not have fully elapsed. For instance, if the time period is one hour, and forty-five minutes have elapsed since a last audit, there may be fifteen minutes left before a current audit is initiated. In the example, at 2712, the first central device 114 may transmit the first audit status 220 to the backend server 116 and the backend server 116 may receive the first audit status 220 from the first central device 114. In the example, the first audit status 220 may indicate that the first asset 102 needs an audit.

[0365] In another example, the A / th central device 126 (FIG. 2) may detect the first signal 110 emitted / transmitted / broadcast by the first peripheral device 106 within the time period defined by the first audit frequency 218 instead of the first central device 114. In the example, the A / th central device 126 may transmit the first audit status 220 to the backend server 116 and the backend server 116 may receive the first audit status 220 from the A th central device 126. In the example, the104WBD (US) 4911-1825-7051first audit status 220 may indicate that the first asset 102 is in the wrong location (i.e., the first asset 102 is expected to be at / around the first jobsite 212, but the first asset 102 is actually located at / around the second jobsite 226).

[0366] Although not depicted in FIG. 27, it is contemplated that the backend server 116 may receive audit statuses for other assets (e g., the Ath asset 104, the second plurality of assets 128) from the first central device 114 and / or other central devices (e.g., the A7th central device 126) in a manner similar to that described above with respect to the first asset 102 and the first central device 114.

[0367] At 2714, the backend server 116 may transmit, to the user device 120 (or another user device), data that includes or that is associated with the first audit status 220 and / or the first asset status 214 and the user device 120 may receive the data that includes or that is associated with the first audit status 220 and / or the first asset status 214. The backend server 116 may also transmit, to the user device 120 (or another user device) data that includes or that is associated with audit statuses and / or asset statuses of other assets and the user device 120 may receive the data that includes or that is associated with the audit statuses and / or the asset statuses of the other assets.

[0368] At 2716, the user device 120 (or another user device) may present a GUI on a display based on the data received at 2714. The GUI may include information pertaining to the first audit status 220 and / or the first asset status 214. The GUI may also include information pertaining to the audit statuses and / or the asset statuses of the other assets. In an example, the GUI may be or include the GUI 123 or the GUI 712.

[0369] In an example, the user device 120 (or another user device) may receive a selection of an element in the GUI and at 2718, the user device 120 may transmit an indication of the selection to the backend server 116 and the backend server 116 may receive the indication of the selection105WBD (US) 4911-1825-7051from the user device 120 (or another user device). At 2720, the backend server 116 may transmit, based on the indication of the selection, further information to the user device 120 (or another user device) and the user device 120 (or another user device) may receive the further information from the backend server 116. In an example, the further information may include details about the first asset 102. At 2722, the user device 120 (or another user device) may update the GUI to include the further information.

[0370] FIG. 28 is a diagram 2800 illustrating an example of a decision flow for asset and audit status management in accordance with some aspects of the present disclosure. In an example, the decision flow may be implemented by the system described in FIG. 1. At 2802, the first central device 114 may determine whether the first central device 114 has detected / sensed / received the first signal 110 emitted / transmitted / broadcast by the first peripheral device 106 of the first asset 102 within a time period defined by an audit frequency. Upon positive determination that the first central device 114 has detected / sensed / received the first signal 110, at 2804, the backend server 116 may update the first audit status 220 for the first asset 102 to be audited.

[0371] Upon negative determination that the first central device 114 has detected / sensed / received the first signal 110, at 2806, thc / V / th central device 126 determines whether the U / th central device 126 has detected / sensed / received the first signal 110 emitted / transmitted / broadcast by the first peripheral device 106 of the first asset 102 within the time period. Upon negative determination that the A th central device 126 has detected / sensed / received the first signal 110, at 2808, the backend server 116 may update the first audit status 220 for the first asset 102 to be overdue. In some aspects, the backend server 116 may cause a notification (e.g., an email, an in-app notification, etc.) to be transmitted to a user device (e.g., the user device 120) that indicates that the first asset 102 is overdue for an audit.106WBD (US) 4911-1825-7051

[0372] Upon positive determination that the AYth central device 126 has detected / sensed / received the first signal 110, at 2810, the backend server 116 may determine whether the first central device 114 and the AYth central device 126 are associated with the same user account (e.g., the first user account 208). Additionally or alternatively, at 2810, the backend server 116 may determine whether the first assignments 210 and the second assignments 224 are associated with the same user account (e.g., the first user account 208).

[0373] Upon negative determination that the first central device 114 and the AYth central device 126 are associated with the same user account (and / or that the first assignments 210 and the second assignments 224 are associated with the same user account), at 2808, the backend server 116 may update the first audit status 220 for the first asset 102 to be overdue.

[0374] Upon positive determination that the first central device 114 and the AYth central device 126 are associated with the same user account (and / or that the first assignments 210 and the second assignments 224 are associated with the same user account), at 2812, the backend server 116 may notify a user of the user account in order to provide the user with an option to reassign the first asset 102 to the second assignments 224 (and / or to the AYth central device 126). For instance, the backend server 116 may transmit a message to the user device 120 that indicates that the first asset 102 has been sensed within the second jobsite 226 and that provides an option to reassign the first asset 102 from the first jobsite 212 to the second jobsite 226 (i.e., reassign the first asset 102 from the first assignments 210 to the second assignments 224).

[0375] At 2814, the backend server 116 may determine whether the backend server 116 has received, from the user device 120, an indication of reassignment of the first asset 102 from the first jobsite 212 to the second jobsite 226. Such determination may involve the passage of a preselected interval of time to allow such an input from the user device 120. Upon negative107WBD (US) 4911-1825-7051determination, at 2816, the backend server 116 may update the first audit status 220 for the first asset 102 to be wrong location. In some aspects, the backend server 116 may cause a notification (e.g., an email, an in-app notification, etc.) to be transmitted to a user device (e.g., the user device 120) that indicates that the first asset 102 is in a wrong location. Upon positive determination, at 2818, the backend server 116 may reassign the first asset 102 from the first jobsite 212 to the second jobsite 226 (i.e., reassign the first asset 102 from the first assignments 210 to the second assignments 224), and at 2804, the backend server 116 may update the first audit status 220 for the first asset 102 to be audited.

[0376] FIG. 29 is a diagram 2900 illustrating an example of a graphical user interface (GUI) for asset and audit status management in accordance with some aspects of the present disclosure. In an example, the GUI 123 and / or the GUI 712 may be or include the GUI depicted in the diagram 2900 (or a portion of the GUI depicted in the diagram 2900). In another example, the GUI presented at 2716 and / or the GUI updated at 2722 may be or include the GUI depicted in the diagram 2900 (or a portion of the GUI depicted in the diagram 2900).

[0377] The GUI depicts asset statuses 2902. In an example, the asset statuses 2902 may correspond to the first asset status 214, the Mh asset status 216, and / or the second asset statuses 225. The asset statuses 2902 may include a plurality of categories of asset statuses. The plurality of categories may include available, deployed, missing, service needed, out for service, and / or lost. The GUI may also display a number of assets belonging to each category. Each of the plurality of categories of asset statuses may be selectable in the GUI. When a category in the plurality of categories is selected, the GUI may be updated to display information about assets belonging to the category. For instance, if the missing category is selected, the GUI may be updated to display information about assets that are missing.108WBD (US) 4911-1825-7051

[0378] The GUI depicts audit statuses 2904. Tn an example, the audit statuses 2904 may correspond to the first audit status 220, the Mh audit status 222, and / or the second audit statuses 227. The audit statuses 2904 may include a plurality of categories of audit statuses. The plurality of categories may include audited, needs audit, overdue, and / or wrong location. The GUI may also display a number of assets belonging to each category. Each of the plurality of categories of audit statuses may be selectable in the GUI. When a category in the plurality of categories is selected, the GUI may be updated to display information about assets belonging to the category. For instance, if the audited category is selected, the GUI may be updated to display information about assets that have been audited. The GUI further depicts a chart 2906 that graphically depicts percentages of assets belonging to each category in the plurality of categories of audit statuses. In the example depicted in the diagram 2900, the chart 2906 indicates that 4.3% of all assets have been audited.

[0379] The GUI further includes an add asset button 2908. When the GUI receives a selection of the add asset button 2908, the GUI may be updated to enable a user to add an asset to assignment(s). The GUI further includes an add assignment button 2910. When the GUI receives a selection of the add assignment button 2910, the GUI may be updated to enable the user to add an assignment to a user account (e.g., the first user account 208).

[0380] The GUI may further include a connected assets field 2912. The connected assets field 2912 may be alternatively referred to as a “coin cell state of charge status” or a “coin cell health widget.” The connected assets field 2912 may include visual indications of a coin cell status. As discussed herein, a connected power tool may include a Bluetooth® Eow Energy Module (BLEM) that is powered by a coin cell and / or another internal battery. The coin cell (or another internal battery) may keep the BLEM powered even when a primary battery pack of the connected power109WBD (US) 4911-1825-7051tool is not present (or is out of charge). If the primary battery pack is present, the BLEM may use the primary battery pack for power for data communication. Assets such as audit chips and / or audit tags may also have internal coin cells. A central device (e.g., the first central device 114) may obtain a coin cell status (i.e., an indication of remaining charge in a coin cell) periodically from a BLEM (i.e., a BLEM device) via an advertisement signal and / or extended scan response signals. The central device may transmit an indication of the coin cell status to the backend server 116, and the backend server may cause the coin cell status to be displayed within the connected assets field 2912 in the GUI. As such, the connected assets field 2912 may provide a graphical representation of a coin cell status of all connected assets associated with a user account (e.g., the first user account 208). In an example, a coin cell status may be “excellent,” “good,” “fair,” or “poor.” In the example GUI depicted in FIG. 29, 1850 coin cells are “excellent,” 1055 coin cells are ’’good,” 201 coin cells are “fair,” and 111 coin cells are “poor,” for a total of 3217 coin cells.

[0381] The GUI may further include a gateway field 2914. The gateway field 2914 may alternatively be referred to as a “gateway widget.” The gateway field 2914 may display information pertaining to all gateways (e.g., the first central device 114, the L / th central device 126, etc.) associated with a user account (e.g., the first user account 208). In some aspects, some, but not all of the gateways may be battery operated (i.e., battery powered). The gateway field 2914 may include an indication of assets seen by (i.e., detected by) gateways in the last seven days. The gateway field 2914 may also display an indication of a charge status of gateways that are battery powered. In an example, a charge status may be greater than 15% charge or less than 15% charge. In the example GUI depicted in FIG. 29, 220 gateways have a charge greater than 15% and 247 gateways have a charge less than 15%. Furthermore, 41 gateways (out of 508 gateways) are not battery powered.110WBD (US) 4911-1825-7051

[0382] FIG. 30 is a diagram 3000 illustrating an example of a GUI for asset status management in accordance with some aspects of the present disclosure. In an example, the GUI 123 and / or the GUI 712 may be or include the GUI depicted in the diagram 800 (or a portion of the GUI depicted in the diagram 3000). In another example, the GUI presented at 2716 and / or the GUI updated at 2722 may be or include the GUI depicted in the diagram 3000 (or a portion of the GUI depicted in the diagram 3000).

[0383] The GUI depicted in the diagram 3000 may be displayed when the available category in the asset statuses 2902 is selected. The GUI depicts, for each asset belonging to the available category, an image, a description, a model number, an assignment name, an inventory number, a category, a quantity, and / or an indication of the asset status (available). Each row in the GUI may correspond to a different asset, and each column in the GUI may correspond to different types of information about an asset.

[0384] Each row in the GUI may be selectable. When a row is selected, the GUI may be updated to display information pertaining to an asset assigned to the row. For example, the GUI may receive a selection of a row 3002, and the GUI may be updated to display information pertaining to the asset assigned to the row 3002.

[0385] FIG. 31 A is a diagram 3100A illustrating an example of a GUI for viewing asset details in accordance with some aspects of the present disclosure. In an example, the GUI 123 and / or the GUI 712 may be or include the GUI depicted in the diagram 3100 A (or a portion of the GUI depicted in the diagram 3100A). In another example, the GUI presented at 2716 and / or the GUI updated at 2722 may be or include the GUI depicted in the diagram 3100A (or a portion of the GUI depicted in the diagram 3100A).111WBD (US) 4911-1825-7051

[0386] The GUI depicted in the diagram 3100A may be displayed when the row 3002 is selected. The GUI may include an identifier for the asset (“20V MAX* COMPACT PRESS TOOL”) corresponding to the row 3002, an asset status for the asset, an assignment status for the asset, a serial number of the asset, and / or a model number for the asset.

[0387] The GUI may further display a manufacturer of the asset, a description of the asset, a category of the asset, a responsible person for the asset, an inventory number of the asset, a barcode for the asset, and / or purchase data for the asset. The GUI may include fields that enable certain details of the asset to be changed. For instance, the fields may include category, asset status, and / or responsible person.

[0388] The GUI may include an assignment tab 3102. When the assignment tab 3102 is selected, the GUI may be updated to display assignment information about the asset.

[0389] FIG. 3 IB is a diagram 3100B illustrating an example of a GUI for viewing assignment details in accordance with some aspects of the present disclosure. In an example, the GUI 123 and / or the GUI 712 may be or include the GUI depicted in the diagram 3100B (or a portion of the GUI depicted in the diagram 3100B). In another example, the GUI presented at 2716 and / or the GUI updated at 2722 may be or include the GUI depicted in the diagram 3100B (or a portion of the GUI depicted in the diagram 3100B).

[0390] The GUI depicted in the diagram 3100B may be displayed when the assignment tab 3102 is selected. The GUI displays an assignment history 3104 for the asset. The assignment history indicates that the asset was assigned on March 7, 2025 at 4:02 PM and unassigned on March 7, 2025 at 4:05 PM. The GUI further includes a field 3106 that enables a user to assign the asset to an assignment.112WBD (US) 4911-1825-7051

[0391] The GUI may include an audit information tab 3108. When the audit information tab 3108 is selected, the GUI may be updated to display audit information about the asset.

[0392] FIG. 32 is a diagram 3200 illustrating an example of a GUI for viewing an audit history of an asset in accordance with some aspects of the present disclosure. In an example, the GUI 123 and / or the GUI 712 may be or include the GUI depicted in the diagram 3200 (or a portion of the GUI depicted in the diagram 3200). In another example, the GUI presented at 2716 and / or the GUI updated at 2722 may be or include the GUI depicted in the diagram 3200 (or a portion of the GUI depicted in the diagram 3200).

[0393] The GUI depicted in the diagram 3200 may be displayed when the audit information tab 3108 is selected. The GUI may include an identifier for an asset, an asset status of the asset, an assignment of the asset, a serial number of the asset, a model number of the asset, a time at which the asset was added to a user account, a MAC address of the asset, an address of the asset, and a last seen date and time of the asset. The GUI may further depict an audit history 3202 for the asset.

[0394] FIG. 33 is a diagram 3300 illustrating an example of a GUI for viewing audit statuses in accordance with some aspects of the present disclosure. In an example, the GUI 123 and / or the GUI 712 may be or include the GUI depicted in the diagram 3300 (or a portion of the GUI depicted in the diagram 3300). In another example, the GUI presented at 2716 and / or the GUI updated at 2722 may be or include the GUI depicted in the diagram 3300 (or a portion of the GUI depicted in the diagram 3300).

[0395] The GUI depicted in the diagram 3300 may be displayed when the wrong location category in the audit statuses 2904 is selected. The GUI depicts, for each asset belonging to the wrong location category, an image, a description, a model number, an assignment name, an inventory number, a category, a quantity, and / or an indication of the asset status (deployed), the asset status,113WBD (US) 4911-1825-7051a date and time of a last audit for the asset, and an identifier for an entity performing the last audit. Each row in the GUI may correspond to a different asset belonging to the wrong location category, and each column in the GUI may correspond to different types of information about an asset.

[0396] Each row in the GUI may be selectable. When a row is selected, the GUI may be updated to display information pertaining to an asset assigned to the row. For example, the GUI may receive a selection of a row 3302, and the GUI may be updated to display information pertaining to the asset assigned to the row 3302. For instance, the GUI may be updated to display information similar to the GUI depicted in FIG. 31 A, FIG. 3 IB, and / or FIG. 32.

[0397] Some aspects presented herein pertain to a site manager that provides tool managers, site supervisors, safety managers, and other construction management professionals with operational information about tools and related accessories in order for the tools / accessories to be operated in a safe and efficient manner. In some aspects, the site manager may receive tool and battery operational information, which can include tool runtime, trigger pulls, voltages, currents, temperatures, shutdowns, safety events, charge levels, voltages, currents, states (charging, idle, in-use, etc.). In some aspects, the tool and battery operational information may tie a tool and a battery together (e.g., tool A was used for X minutes with battery Y).

[0398] The site manager may surface operational information and recommendations to users based on the tool and battery operational information. For example, if a tool has zero runtime in the past week, the tool may be a candidate to move to another site. When the tool is moved to another site, the site manager may determine that the tool, when last ran, used an average of two batteries per day, and as such, the site manager may suggest that a user move two batteries along with the tool. In another example, a tool may need service every hundred hours. Based on historical data, the site manager may determine that the tool is operated for twenty hours on a jobsite. If the tool114WBD (US) 4911-1825-7051currently has eighty-five hours since last service, the site manager may suggest that the tool be serviced before the tool is sent to a jobsite again. In another example, the site manager may determine an average amount of shutdowns / faults for a given model of tool. If a tool reports a value above the average amount of shutdown / faults, the site manager may provide an alert to a user indicating that the tool should be taken in for service.

[0399] In some aspects presented herein, the site manager may allow a user to set a flag for each asset (e.g., a tool, a battery, etc.) as available (one that is not assigned to a project or a task), deployed (deployed to an assignment), missing (not yet flagged as lost), requires service, out for service, or lost. The site manager may enable the user to view all asset with the same status (e.g., all available assets, all lost assets, etc.) at one time. In an example, the user may click on an available asset and the site manager may display an inventory table that displays only available assets. The site manager may change the asset status from available to another status based on input from the user. The site manager may also assign an asset to a project / task / assignment based on input from the user. In some examples, when a tool is assigned to an assignment, the site manager may change a status for the tool to deployed. The assignment may include location information for a jobsite where the tool is expected to be located.

[0400] In some aspects presented herein, the site manager may provide an audit panel that enables a user to view an audit status of an asset. When a gateway (or a mobile application of a user that acts as a gateway) at a jobsite scans an asset, the audit information of the asset may be automatically updated. The audit information may include a date, a time, and a location of the scan. Each time an asset is scanned by a gateway, the audit information may be updated. The site manager may receive input from a user that is indicative of assets that have been audited, need to be audited, are overdue for an audit, or are in a wrong location. An assignment may include, in115WBD (US) 4911-1825-7051addition to a job site address and other assignment information, an audit frequency (e.g., daily, weekly, biweekly, monthly, etc.) for an asset. If a tool has not been scanned at a jobsite for a period longer than the audit frequency, the asset may be flagged as “needs audit.” If it is not scanned for a much longer period, the asset may be flagged as “overdue for audit.” If the asset is scanned by a gateway that is located at a location that does not match an inventory location for the asset, the asset may be flagged as “wrong location.”

[0401] FIG. 34 is a communication flow diagram 3400 that illustrates example communications between the construction assets 902, the gateway 904, the backend server 116, and the user device 120 for presenting a GUI that depicts a map of the construction assets 902 and audit statuses for the construction assets 902 in accordance with some aspects of the present disclosure.

[0402] At 3402, the construction assets 902 emit (and the gateway 904 receives) advertisement signals. The actions performed at 3402 may be similar or identical to the actions performed at 906 in the description of FIG. 9 and / or the actions performed at 2710 in the description of FIG. 27.

[0403] At 3406, the gateway 904 transmits (and the backend server 116 receives) audit statuses for the construction assets 902. The actions performed at 3402 may be similar or identical to the actions performed at 2712 in the description of FIG. 27.

[0404] At 3408, the backend server 116 generates a GUI that depicts a map of the construction assets and audit statuses for the construction assets. The backend server 116 may utilize a third-party mapping service (not depicted in FIG. 34) to generate the map based on the audit statuses. Details pertaining to contents of the GUI are described in greater detail below in the description of FIGs. 35-43. In some aspects, the GUI may be a part of site manager as described herein. At 3410, the backend server 116 transmits (and the user device 120 receives) the GUI. At 3412, the user device 120 displays the GUI on a display. At 3414, GUI interaction(s) occur. The GUI116WBD (US) 4911-1825-7051interactions may include receiving input at the user device 120 and / or communications (transmitting and / or receiving data associated with the GUI) between the backend server 116 and the user device 120. The GUI interactions may be associated with enabling the display of all construction assets belonging to an enterprise user that are visible on the map, filtering the construction assets displayed in the map based on assignments, audit statuses, and / or responsible parties, viewing audit statuses of the construction assets, and / or updating the displayed construction assets on the map based on zooming in and / or zooming out on the map. Details pertaining to the GUI interaction(s) are described in greater detail below in the description of FIGs.35-43.

[0405] FIG. 35 is a diagram 3500 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. The GUI depicted in FIG. 35 may be a default view displayed before the construction assets 902 have been added to a user account and / or before details pertaining to the construction assets 902 have been loaded. The GUI includes a map 3502 with a first view. The GUI may include controls 3504 that enable the map 3502 to be zoomed-in and / or zoomed-out. In an example, the user device 120 receives a selection of the controls 3504 that causes the map 3502 to be zoomed-in to a particular location that includes the construction assets 902, leading the user device 120 to present the GUI depicted in FIG. 36.

[0406] FIG. 36 is a diagram 3600 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. The GUI depicted in FIG. 36 includes the map 3502 with a second view, where the second view is a zoomed-in version of the first view. In an example, the circles illustrated in the GUI represent assignments. The map 3502 now includes first visual indications117WBD (US) 4911-1825-70513602 of a portion of the construction assets 902 that are physically located within the geographic area displayed in the map 3502 and that are located in correct locations (e.g., locations included in an assignment). The map 3502 also includes second visual indications 3604 of a portion of the construction assets 902 that are physically located within the geographic area displayed in the map 3502, but that are not in the correct locations (e.g., as determined by an audit performed by a gateway, a lack of receiving a signal from construction assets within a predetermined time period, etc.). The GUI includes an indication of how many construction assets are in the second view. The GUI also includes a side panel 3606 that displays information about each of the construction assets (one-hundred and eighteen construction assets) visible in the second view of the map 3502. The information about each of the construction assets visible in the second view of the map 3502 may include an identifier for a construction asset, a name of an assignment of the construction asset, a type of the construction asset, an audit status for the construction asset (e.g., audited, wrong location, etc.), and a time of a last audit for the construction asset. In an example, the user device 120 receives a selection of the controls 3504 that causes the map 3502 to be zoomed-in to a particular location that includes a portion of the construction assets 902 displayed in the map 3502 in FIG. 36, leading the user device 120 to present the GUI depicted in FIG. 37.

[0407] FIG. 37 is a diagram 3700 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. The GUI depicted in FIG. 37 includes the map 3502 with a third view, where the third view is a zoomed-in version of the second view. The map 3502 now includes first visual indications 3702 (including a first visual indication 3702A, explained in greater detail below) and second visual indications 3704, which are similar to the first visual indications 3602 and the second visual indications 3604, respectively, but are for the third view of the map 3502 (as118WBD (US) 4911-1825-7051opposed to the second view). The side panel 3606 now displays information about construction assets (now fifty-seven construction assets) visible in the third view of the map 3502.

[0408] The GUI includes an assignment filter 3706, an audit status filter 3708, and a responsible person filter 3710. The assignment filter 3706 enables the map 3502 to be filtered for construction assets based on assignments. The audit status filter 3708 enables the map 3502 to be filtered for construction assets based an audit status. The responsible person filter 3710 enables the map 3502 to be filtered for responsible persons. In an example, the assignment filter 3706, the audit status filter 3708, and the responsible person filter 3710 may be automatically applied to the map 3502 when zooming-in and / or zooming-out (i.e., when transitioning between views of the map 3502). In an example, the user device 120 receives input which causes the mouse cursor to be positioned over a second visual indication 3704A, leading the user device 120 to present the GUI depicted in FIG. 38.

[0409] FIG. 38 is a diagram 3800 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. When the mouse cursor is positioned over the second visual indication 3704A and / or when the second visual indication 3704A is selected, the GUI display a pop-up window 3802A corresponding to the construction asset associated with the second visual indication 3704A. The pop-up window 3802A may display, for the construction asset associated with the second visual indication 3704A, an identifier for the construction asset, a name of an assignment of the construction asset, a type of the construction asset, an audit status for the construction status (e.g., wrong location), a time of a last audit for the construction asset, an identifier for a gateway that last audited the construction asset, and / or a distance of the construction asset from an expected location of the construction asset. The GUI may also highlight an entry119WBD (US) 4911-1825-70513802B for the construction asset in the side panel 3606 responsive to the cursor being positioned over the second visual indication 3704A and / or the second visual indication 3704A being selected.

[0410] In an example, the user device 120 receives a selection of the first visual indication 3702A, leading the user device 120 to present the GUI depicted in FIG. 39. The first visual indication 3702A corresponds to an assignment of construction assets maintained by the backend server 116.

[0411] FIG. 39 is a diagram 3900 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. The GUI depicted in FIG. 39 includes the map 3502 with a fourth view, where the fourth view is a zoomed-in version of the third view. As the first visual indication 3702A corresponds to an assignment, the assignment filter 3706 is automatically updated to a “downtown construction” assignment maintained by the backend server 116, and the user device 120 automatically filters the map for the “downtown construction” assignment based on the selection of the first visual indication 3702A. The side panel 3606 now displays information about construction assets (now thirty -five construction assets) visible in the fourth view of the map 3502. The GUI displays first visual indications 3902 (including a first visual indication 3902A, described below) which are similar to the first visual indications 3602, but are for the fourth view of the map 3502 (as opposed to the third view). The GUI displays a second visual indication 3904 for a construction asset that is in a wrong location (as determined by an audit).

[0412] The GUI includes a show assignment toggle bar 3906. In an example, the user device 120 receives input which toggles the show assignment toggle bar 3906 from an on position to an off position, leading the user device 120 to display the GUI depicted in FIG. 40.

[0413] FIG. 40 is a diagram 4000 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects120WBD (US) 4911-1825-7051of the present disclosure. The GUI depicted in FIG. 40 shows a circle 4002 (or another shape) corresponding to the “downtown” construction assignment, in order to enable the user to visualize which construction assets are located in correct locations as determined by the assignment. As illustrated in FIG. 40, the second visual indication 3904 is located outside of the circle 4002, indicating that the construction asset corresponding to the second visual indication 3904 is in the wrong location. The GUI also depicts an identifier 4004 for the “downtown construction” assignment.

[0414] In an example, the user device 120 receives input which causes a mouse cursor to hover over and / or select the first visual indication 3902A, leading the user device 120 to display the GUI depicted in FIG. 41.

[0415] FIG. 41 is a diagram 4100 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. The GUI depicted in FIG. 41 displays a pop-up window 4102 corresponding to the construction asset associated with the first visual indication 3902A. The popup window 4102 may include information similar to the pop-up window 3802A.

[0416] In an example, the user device 120 receives input which causes a mouse cursor to hover over and / or select the second visual indication 3904, leading the user device 120 to display the GUI depicted in FIG. 42.

[0417] FIG. 42 is a diagram 4200 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. The GUI in FIG. 42 includes a pop-up window 4202 for the construction asset corresponding to the second visual indication 3904. The pop-up window 4202 may include information similar to the pop-up window 3802A. In the example depicted in FIG. 42, the pop-up121WBD (US) 4911-1825-7051window 4202 indicates that the construction asset is in the wrong location (as determined by an audit). The pop-up window 4202 includes a transfer assignment button 4204 that enables the construction asset to be transferred to a different assignment. In an example, the user device 120 receives a selection of the transfer assignment button 4204, leading the user device 120 to display the GUI depicted in FIG. 43.

[0418] FIG. 43 is a diagram 4300 illustrating an example of a GUI for depicting a map of the construction assets and audit statuses for the construction assets in accordance with some aspects of the present disclosure. The GUI depicted in FIG. 43 displays a transfer window 4302 that enables the construction asset corresponding to the second visual indication 3904 to be transferred to a different assignment (e.g., such that the map 3502 no longer displays the construction asset as being in the wrong location). The transfer window 4302 includes fields 4304 for receiving input pertaining to details of the assignment transfer. The fields 4304 include a field for specifying and / or receiving an identifier of the assignment to which the construction asset is to be transferred, an effective date of the transfer, an asset status for the construction asset, a person to be responsible for the construction asset upon the transfer being completed, and notes pertaining to the transfer. In an example, the user device 120 receives input to the fields 4304 specifying details of the assignment transfer. The user device 120 receives a selection of a transfer button 4306 in the transfer window 4302. The selection causes the user device 120 to transmit data set forth in the fields 4304 (and an identifier for the construction device) to the backend server 116. The backend server 116 receives the data and causes the construction asset to be assigned to the assignment specified in the data set forth to the fields 4304.

[0419] FIG. 44 is a communication flow diagram 4400 that illustrates example communications between the construction assets 902, the gateway 904, the backend server 116, and the user device122WBD (US) 4911-1825-7051120 for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure.

[0420] At 4402, the backend server transmits (and the user device 120 receives) a GUI configured to receive a construction asset category and a service plan for construction assets belonging to the construction asset category. At 4404, the user device 120 presents the GUI on a display. In an example, the GUI is a GUI depicted in FIG. 47A and / or FIG. 47B (described below).

[0421] At 4406, the user device 120 receives a construction asset category (e.g., torque ranges, concrete screeds, etc.) and a service plan as input to the GUI. In an example, the construction assets 902 belong to the construction asset category. In some aspects, the construction asset category is a component within a power tool including many different components that work in conjunction with one another to provide a functionality. The service plan may include a name of the service plan, the construction asset category, a type of service (e.g., safety, regular maintenance, etc.), information about an entity that is to perform the service, and / or a schedule. The schedule may indicate an interval at which reminders for the service plan are to be transmitted. For instance, the schedule may be based on a recurring time period (e.g., every month, every three months, every year, etc.), a number of runtime hours for construction assets belonging to the construction asset category, and / or a number of cycles for construction assets belonging to the construction asset category. In some aspects, the schedule may also indicate identifiers for person(s) (e.g., administrators, site administrators, managers, a person responsible for the construction assets, an assignment point of contact, etc.) that are to be notified when service is due for construction assets belonging to the construction asset category, a number of notifications that are to be sent, a number of days that the person(s) are to be notified before service is due, and / or a type of the notification (e.g., a text message, an email, a reminder within a dashboard, etc.).123WBD (US) 4911-1825-7051

[0422] At 4408, the user device 120 transmits (and the backend server 116 receives) the construction asset category and the service plan for the construction asset category. The user device 120 may also transmit (and the backend server 116 may also receive) an identifier for a user account. At 4410, the backend server 116 applies the service plan to construction assets (e.g., all construction assets) associated with a user account that belong to the construction asset category. For instance, the backend server 116 may execute a search over construction asset-associated data maintained by the backend server 116 based on the construction asset category and the user account. The search produces search results that include construction assets of the user account that belong to the construction asset category. The backend server 116 may create a link between each construction asset belonging to the construction asset category such that the backend server 116 associates each construction asset belonging to the construction asset category with the service plan. The backend server 116 may record a timestamp at which the service plan is applied to each construction asset belonging to the construction asset category.

[0423] In some aspects, at 4412, the construction assets 902 may emit (and the gateway 904 may receive) advertisement signals that include indications of operational runtimes of the construction assets 902. An indication of an operational runtime of a construction asset in the construction assets 902 may include a time duration (e.g., in hours, days, weeks, months, etc.) and / or a number of cycles run by the construction asset. At 4414, the gateway 904 may transmit (and the backend server 116 may receive) the indication of the operational runtimes for the construction assets 902.

[0424] At 4416, the backend server 116 determines that a construction asset (e.g., in the construction assets 902) belonging to the construction asset category is due for service based on the service plan. In an example, the backend server 116 may determine that a time between the timestamp at which the service plan was applied and a current timestamp exceeds a time period in124WBD (US) 4911-1825-7051the service plan, and as such, the backend server 116 determines that the construction asset is due for service. In another example, the backend server 116 may access a timestamp of a last service of the construction asset maintained by the backend server 116. The backend server 116 may determine that a time between the timestamp of the last service of the construction asset and a current timestamp exceeds a time period in the service plan, and as such, the backend server 116 determines that the construction asset is due for service. In another example, the backend server 116 compares a number of runtime hours (e.g., received at 4414) for the construction asset to a number of runtime hours in the service plan. The backend server 116 may determine that the number of runtime hours (received at 4414) for the construction asset is greater than the number of runtime hours in the service plan, and as such, the backend server 116 determines that the construction asset is due for service. In a further example, the backend server 116 compares a number of cycles (received at 4414) for the construction asset to a number of cycles in the service plan. The backend server 116 may determine that the number of cycles (received at 4414) for the construction asset is greater than the number of cycles in the service plan, and as such, the backend server 116 determines that the construction asset is due for service.

[0425] At 4418, based on the determination at 4416, the backend server 116 may transmit (and the user device 120 may receive) a notification indicating that the construction asset is due for service. The notification may be based on the service plan received at 4408 and applied at 4410. In an example, the notification may include an identifier for the construction asset, a type of service that is due, and information about an entity that is to perform the service (e.g., contact information, such as a phone number, an email address, a physical address, etc.). Additionally or alternatively, the backend server 116 may transmit the notification to other user devices (not depicted in FIG. 1) based on the service plan.125WBD (US) 4911-1825-7051

[0426] At 4420, the user device 120 may present the notification to a user. For instance, the user device 120 may display the notification (e.g., within a dashboard), emit the notification over a speaker, vibrate, etc. In some aspects, the notification may be a text message.

[0427] Subsequently, it is contemplated that the construction asset undergoes the service specified by the service plan. For instance, a person responsible for the construction asset make take the construction asset for service. At 4422, the user device may transmit (and the backend server 116 may receive) an indication that service has been completed for the construction asset. In some aspects, the user device 120 may present a GUI such as the GUI depicted in FIG. 48. The GUI may receive, as input, data pertaining to the completion of the service for the construction asset and the indication transmitted at 4422 may include such data. At 4424, the backend server 116 may update information for the construction asset (maintained by the backend server 116 as part of a user account) to indicate that the construction asset has undergone service. For instance, the backend server 116 may record a timestamp at which the service was completed for the construction asset. The backend server 116 may use the timestamp to perform the actions at 4416 and 4418 again to facilitate regular service / maintenance for the construction asset.

[0428] In some aspects, at 4426, the backend server 116 and the user device 120 may onboard a new construction asset belonging to the construction asset category in the service plan applied at 4410. In an example, the onboarding may be an onboarding process described herein. At 4428, as part of the onboarding process, the backend server 116 may automatically apply the service plan to the new construction asset based on a determination that the new construction asset belongs to the construction asset category in the service plan.

[0429] FIG. 45 is a diagram 4500 illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure. The126WBD (US) 4911-1825-7051user device 120 may present the GUI depicted in FIG. 46. The GUI includes information about construction assets. In an example, the user device 120 receives a selection of a row 4502 corresponding to a construction asset (e.g., a safety harness), leading the user device 120 to present the GUI depicted in FIG. 46.

[0430] FIG. 46 is a diagram 4600 illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure. The GUI depicted in FIG. 36 includes a service plan pane 4602 for the construction asset selected in FIG. 45. The service plan pane 4602 may include a name of a service plan (e.g., safety gear inspection, part change, maintenance protocol, etc.), a time period for which the service plan recurs, a date of last service of the construction asset, a due date for the next service for the construction asset, a type of the service plan, an indication of whether the construction asset is currently up to date on service, and / or an identifier for a user that created the service plan for the construction asset. In an example, the service plan for the construction asset may be the service plan applied at 4410 in FIG. 44.

[0431] The service plan pane 4602 may include an apply service plan button 4604. When the GUI depicted in FIG. 46 receives a selection of the apply service plan button 4604, the user device 120 may present the GUI depicted in FIG. 47A and FIG. 47B that enables a user to generate and apply a service plan to all construction assets belonging to a particular construction asset category as described at 4402-4410 in the description of FIG. 44. The service plan pane 4602 may include a complete service button 4606. When the GUI depicted in FIG. 46 receives a selection of the complete service button 4606, the user device 120 may present the GUI depicted in FIG. 49 that enables the user to record that service for the construction asset has been completed as in 4422 in FIG. 44.127WBD (US) 4911-1825-7051

[0432] The GUT may also include a service history pane 4608. The service history pane 4608 may include a date of each service undergone by the construction asset, a name of the service plan, an identifier for a person that performed the service, and attachments associated with the service.

[0433] FIG. 47A is a diagram 4700A illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure. FIG. 47B is a diagram 4700B illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure. The user device 120 may present the GUI depicted in FIG. 47A and FIG. 47B upon receiving a selection of the apply service plan button 4604 in the GUI depicted in FIG. 46.

[0434] The GUI depicted in FIG. 47A and FIG. 47B may correspond to the GUI referred to at 4404 and 4406 in FIG. 44. The GUI may include service plan details fields 4702. The service plan details fields 4702 may include a field for receiving a name of a service plan to be applied, a field for receiving a type of the service plan, and a field for receiving a construction asset category for which the service plan is to be applied. The GUI may include schedule fields 4704 for receiving information about a schedule of the service plan. For instance, the schedule fields 4704 may include fields that enable a user to set conditions associated with notifications that service is due. The conditions may be associated with sending notifications at recurring intervals (e.g., monthly, every three months, yearly, etc.). The conditions may be associated with sending notifications after a certain number of runtime hours for a construction asset have elapsed (e.g., based on the operational runtimes at 4414 in FIG. 44). The conditions may be associated with sending notifications after a number of cycles have occurred. The GUI may include alerts fields 4706 for receiving information about persons to which the notifications about service are to be sent. The GUI may also include a notes field 4708 for receiving notes about the service plan and / or the128WBD (US) 4911-1825-7051construction assets. After receiving data input to at least the service plan details fields 4702 and the schedule fields 4704 (e.g., at 4406), the user device 120 may transmit (e.g., at 4408) such data input to the backend server 116, which may apply the service plan at 4410 described above based on the data input.

[0435] FIG. 48 is a diagram 4800 illustrating an example of a GUI for applying a service plan to a category of construction assets in accordance with some aspects of the present disclosure. The user device 120 may present the GUI depicted in FIG. 48 upon receiving a selection of the complete service button 4606 in the GUI depicted in FIG. 46. It is contemplated that the complete service button 4606 is selected after the construction asset depicted in FIG. 46 undergoes service in accordance with a service plan.

[0436] The GUI depicted in FIG. 48 includes a complete service window 4802. The complete service window 4802 includes a name of the service plan and a due date of the service plan. The complete service window 4802 may include a date at which service for the construction asset was performed, an indication of the service provider, and / or a service person responsible for the service, notes / attachments pertaining to the service. After receiving data input to the fields in the complete service window 4802, the user device 120 may transmit such data to the backend server 116 (e.g., at 4422) upon receive a selectin of a complete service button 4804 displayed in the complete service window 4802.

[0437] FIG. 49 is a flow diagram 4900 of a method performed by a backend server for asset onboarding in accordance with some aspects of the present disclosure. The method may be performed by processing logic that may include hardware (e.g., a processing device), software (e.g., instructions running / executing on a processing device), firmware (e.g., microcode), or a129WBD (US) 4911-1825-7051combination thereof. In some aspects, at least a portion of the method may be performed by the backend server 116, the computer system 5600, or a combination thereof.

[0438] The method illustrates example functions used by various embodiments. Although specific function blocks ("blocks") are disclosed in the method, such blocks are examples. That is, embodiments are well suited to performing various other blocks or variations of the blocks recited in the method. It is appreciated that the blocks in the method may be performed in an order different than presented, and that not all of the blocks in the method may be performed.

[0439] At block 4902, a backend server receives, from a gateway, an identifier for a user account and identifiers for a plurality of construction assets detected by the gateway within a range of the gateway, wherein the user account is maintained by the backend server. For example, FIG. 9 at 914 shows that the backend server 116 receives, from the gateway 904, an identifier for a user account and identifiers for a plurality of construction assets detected by the gateway within a range of the gateway, wherein the user account is maintained by the backend server. In an example, the user account may be or include the first user account 208. In an example, the plurality of construction assets may be or include the plurality of assets 102-104. In an example, the identifiers for a plurality of construction assets may be or include the first asset ID 1012 and / or the Ath asset ID 1014.

[0440] At block 4904, the backend server determines that at least one construction asset in the plurality of construction assets is not associated with the user account based on the identifier for the user account and the identifiers for the plurality of construction assets. For example, FIG. 9 at 916 shows that the backend server 116 determines that at least one construction asset in the plurality of construction assets is not associated with the user account based on the identifier for the user account and the identifiers for the plurality of construction assets.130WBD (US) 4911-1825-7051

[0441] At block 4906, the backend server associates an identifier for the at least one construction asset with the user account based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the user account. For example, FIG. 9 at 920 shows that the backend server 116 associates an identifier for the at least one construction asset with the user account based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the user account.

[0442] In some aspects, the backend server may determine that the at least one construction asset in the plurality of construction assets is not associated with additional user accounts maintained by the backend server based on the identifiers for the plurality of construction assets, wherein associating the identifier for the at least one construction asset with the user account may additionally be based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the additional user accounts. For example, FIG. 9 at 918 shows that the backend server may determine that the at least one construction asset in the plurality of construction assets is not associated with additional user accounts maintained by the backend server based on the identifiers for the plurality of construction assets, wherein associating the identifier for the at least one construction asset with the user account at 920 may additionally be based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the additional user accounts.

[0443] In some aspects, the backend server may receive, from a user device, information pertaining to the at least one construction asset subsequent to associating the at least one construction asset with the user account. For example, FIG. 9 at 928 shows that the backend server 116 may receive, from the user device 120, information pertaining to the at least one construction asset subsequent to associating the at least one construction asset with the user account.131WBD (US) 4911-1825-7051

[0444] In some aspects, the backend server may associate the information pertaining to the at least one construction asset with the identifier for the at least one construction asset associated with the user account. For example, FIG. 9 at 934 shows that the backend server 116 may associate the information pertaining to the at least one construction asset with the identifier for the at least one construction asset associated with the user account.

[0445] In some aspects, the backend server may receive, from the user device and prior to receiving the information pertaining to the at least one construction asset, a request for a GUI for entering the information pertaining to the at least one construction asset. For example, FIG. 9 at 924 shows that the backend server 116 may receive, from the user device 120 and prior to receiving the information pertaining to the at least one construction asset, a request for a GUI for entering the information pertaining to the at least one construction asset.

[0446] In some aspects, the backend server may cause the GUI for entering the information pertaining to the at least one construction asset to be presented on the user device. For example, FIG. 9 at 926 shows that the backend server 116 may cause the GUI for entering the information pertaining to the at least one construction asset to be presented on the user device. In an example, the GUI may be or include the GUI 712. In an example, the information pertaining to the at least one construction asset may be or include the first asset information 1017 and / or the TVth asset information 1018.

[0447] In some aspects, the backend server may execute a search over a log of construction asset information based on the identifier for the at least one construction asset. For example, FIG. 9 at 930 shows that the backend server 116 may execute a search over a log of construction asset information based on the identifier for the at least one construction asset.132WBD (US) 4911-1825-7051

[0448] In some aspects, the backend server may identify information pertaining to the at least one construction asset based on search results for the search. For example, FIG. 9 at 932 shows that the backend server 116 may identify information pertaining to the at least one construction asset based on search results for the search.

[0449] In some aspects, the backend server may associate the information pertaining to the at least one construction asset with the identifier for the at least one construction asset associated with the user account. For example, FIG. 9 at 934 shows that the backend server 116 may associate the information pertaining to the at least one construction asset with the identifier for the at least one construction asset associated with the user account.

[0450] In some aspects, the identifier for the at least one construction asset may comprise a MAC address. For example, the first asset ID 1012 may be or include a first MAC address and the Ath asset ID 1014 may be or include an Ath MAC address.

[0451] In some aspects, the plurality of construction assets may comprise at least one of tools or battery packs. For example, the construction assets 902 may be or include tools and / or battery packs. In an example, the plurality of construction assets may include the power tool 302, the power tool 402, and / or the battery pack 602.

[0452] In some aspects, the gateway may comprise a smartphone. For example, the gateway 904 may be a smartphone.

[0453] In some aspects, the backend server may transmit, to a user device, an indication that the at least one construction asset has been associated with the user account. For example, FIG. 9 at 922 shows that the backend server 116 may transmit, to the user device 120, an indication that the at least one construction asset has been associated with the user account.133WBD (US) 4911-1825-7051

[0454] FIG. 50 is a flow diagram 5000 of a method performed by a gateway for asset onboarding in accordance with some aspects of the present disclosure. The method may be performed by processing logic that may include hardware (e.g., a processing device), software (e.g., instructions running / executing on a processing device), firmware (e.g., microcode), or a combination thereof. In some aspects, at least a portion of the method may be performed by the first central device 114, the ATth central device 126, the gateway 502, the first CD 806, the second CD 808, the third CD 810, the fourth CD 818, the gateway 904, the user device 120, the first gateway 1804, the computer system 5600, or a combination thereof.

[0455] The method illustrates example functions used by various embodiments. Although specific function blocks ("blocks") are disclosed in the method, such blocks are examples. That is, embodiments are well suited to performing various other blocks or variations of the blocks recited in the method. It is appreciated that the blocks in the method may be performed in an order different than presented, and that not all of the blocks in the method may be performed.

[0456] At block 5002, a gateway performs, via a wireless controller of the gateway, a scan. For example, FIG. 9 at 910 shows that the gateway 904 performs, via a wireless controller of the gateway, a scan. In an example, the wireless controller may be, may include, and / or may be associated with the BLE transceiver 506.

[0457] At block 5004, the gateway obtains identifiers for a plurality of construction assets within a range of the gateway based on scan results for the scan, wherein at least one construction asset in the plurality of construction assets is not associated with a user account maintained by a backend server. For example, FIG. 9 at 910 shows that the gateway 904 obtains identifiers for a plurality of construction assets within a range of the gateway based on scan results for the scan, wherein at least one construction asset in the plurality of construction assets is not associated with a user 134WBD (US) 4911-1825-7051account maintained by a backend server. In an example, the plurality of construction assets may be or include the plurality of assets 102-104. In an example, the identifiers for the plurality of construction assets may include the first asset ID 1012 and the Afth asset ID 1014. In an example, the user account may be the first user account 208.

[0458] At block 5006, the gateway transmits, to the backend server, an identifier for the user account and the identifiers for the plurality of construction assets. For example, FIG. 9 at 914 shows that the gateway 904 transmits, to the backend server 116, an identifier for the user account and the identifiers for the plurality of construction assets.

[0459] In some aspects, the gateway may receive, from a user device, a command to perform the scan, wherein performing the scan is based on the command. For example, FIG. 9 at 908 shows that the gateway 904 may receive, from the user device 120, a command to perform the scan, wherein performing the scan at 910 is based on the command. In an example, the command may be or include the scan command 1302.

[0460] In some aspects, the gateway may comprise a smartphone, and the gateway may receive user input indicative of the scan, wherein performing the scan is based on the user input. For example, the gateway 904 may be a smartphone.

[0461] In some aspects, performing the scan may comprise receiving a plurality of advertisement signals emitted by the plurality of construction assets, wherein the plurality of advertisement signals may include the identifiers for the plurality of construction assets. For example, performing the scan at 910 may comprise receiving a plurality of advertisement signals emitted by the plurality of construction assets, wherein the plurality of advertisement signals may include the identifiers for the plurality of construction assets. In an example, the plurality of advertisement signals may include the first advertisement signal 1202 and the Ath advertisement signal 1204.135WBD (US) 4911-1825-7051

[0462] In some aspects, the gateway may receive, from the backend server, an indication that the at least one construction asset has been associated with the user account. For example, FIG. 9 at 922 indicates that the user device 120 (which may be the gateway 904) may receive, from the backend server 116, an indication that the at least one construction asset has been associated with the user account.

[0463] In some aspects, the gateway may comprise a smartphone, and the gateway may receive, as user input, information pertaining to the at least one construction asset. For example, the gateway 904 may be a smartphone that receives, as user input, information pertaining to the at least one construction asset.

[0464] In some aspects, the gateway may comprise a smartphone, and the gateway may transmit, to the backend server, the information pertaining to the at least one construction asset for association with the at least one construction asset in the user account. For example, FIG. 9 at 928 shows that the user device 120 (which may be the gateway 904) may transmit, to the backend server 116, the information pertaining to the at least one construction asset for association with the at least one construction asset in the user account.

[0465] In some aspects, the gateway may transmit, to the backend server, a request for a GUI for entering the information pertaining to the at least one construction asset. For example, FIG. 9 at 924 shows that the user device 120 (which may be the gateway 904) may transmit, to the backend server 116, a request for a GUI for entering the information pertaining to the at least one construction asset. In an example, the GUI may be or include the GUI 712. In an example, the information pertaining to the at least one construction asset may be the asset onboarding information 720. In another example, the information pertaining to the at least one construction asset may be or include the first asset information 1017 and / or the JVth asset information 1018.136WBD (US) 4911-1825-7051

[0466] In some aspects, the gateway may receive, from the backend server and based on the request, graphical data. For example, FIG. 9 shows that the user device 120 (which may be the gateway 904) may receive, from the backend server 116 and based on the request, graphical data.

[0467] In some aspects, the gateway may present the GUI based on the graphical data, wherein the GUI may receive the information pertaining to the at least one construction asset. For example, the GUI may be the GUI 712.

[0468] In some aspects, the identifiers for the plurality of construction assets may comprise MAC addresses. For example, the first asset ID 1012 and the Mh asset ID 1014 may be MAC addresses.

[0469] In some aspects, the plurality of construction assets may comprise at least one of tools or battery packs. For example, the construction assets 902 may be or include tools and / or battery packs. In an example, the plurality of construction assets may include the power tool 302, the power tool 402, and / or the battery pack 602.

[0470] FIG. 51 is a flow diagram 5100 of a method performed by a backend server for tracking power tool emissions in accordance with some aspects of the present disclosure. The method may be performed by processing logic that may include hardware (e.g., a processing device), software (e.g., instructions running / executing on a processing device), firmware (e.g., microcode), or a combination thereof. In some aspects, at least a portion of the method may be performed by the backend server 116, the computer system 5600, or a combination thereof.

[0471] The method illustrates example functions used by various embodiments. Although specific function blocks ("blocks") are disclosed in the method, such blocks are examples. That is, embodiments are well suited to performing various other blocks or variations of the blocks recited137WBD (US) 4911-1825-7051in the method. It is appreciated that the blocks in the method may be performed in an order different than presented, and that not all of the blocks in the method may be performed.

[0472] At block 5102, a backend server receives, from a gateway, indications of runtimes of a plurality of power tools that are powered via electricity from a power grid and an indication of a location of the plurality of power tools. For example, FIG. 15 at 1506 shows that the backend server 116 receives, from the gateway 502, indications of runtimes of a plurality of power tools that are powered via electricity from a power grid and an indication of a location of the plurality of power tools. In an example, the plurality of power tools may be or include the power tools 1502.

[0473] At block 5104, the backend server obtains, based on the indication of the location of the plurality of power tools, an estimate of emissions associated with the power grid. For example, FIG. 15 at 1508 shows that the backend server 116 obtains, based on the indication of the location of the plurality of power tools, an estimate of emissions associated with the power grid.

[0474] At block 5106, the backend server calculates a carbon dioxide equivalent emissions of the plurality of power tools over a period of time based on the indications of the runtimes, energy consumptions of the plurality of power tools, and the estimate of the emissions associated with the power grid. For example, FIG. 15 shows that the backend server 116 calculates a carbon dioxide equivalent emissions of the plurality of power tools over a period of time based on the indications of the runtimes, energy consumptions of the plurality of power tools, and the estimate of the emissions associated with the power grid. In an example, the period of time may be or include a year, a month, a day, or some other time period.

[0475] At block 5108, the backend server presents a GUI that depicts graphical information pertaining to the carbon dioxide equivalent emissions of the plurality of power tools. For example,138WBD (US) 4911-1825-7051FIG. 15 at 1 18 shows that the backend server 116 may cause a GUT to be presented that depicts graphical information pertaining to the carbon dioxide equivalent emissions of the plurality of power tools. In an example, the GUI may be or include the GUI depicted in the diagram 1600 and / or the GUI depicted in the diagram 1700.

[0476] In some aspects, obtaining the estimate of the emissions associated with the power grid may include determining, based on the location of the plurality of power tools, a geographic region that encompasses the location of the plurality of power tools. For example, obtaining the estimate of the emissions associated with the power grid at 1508 may include determining, based on the location of the plurality of power tools, a geographic region that encompasses the location of the plurality of power tools. In an example, the location of the plurality of power tools may be GPS coordinate(s), and the geographic region may be a ZIP code.

[0477] In some aspects, obtaining the estimate of the emissions associated with the power grid may include transmitting, to a power profile service, an indication of the geographic region. For example, the aforementioned aspects may correspond to 1508 in FIG. 15.

[0478] In some aspects, obtaining the estimate of the emissions associated with the power grid may include receiving, from the power profile service, the estimate of the emissions associated with the power grid based on the indication of the geographic region. For example, the aforementioned aspects may correspond to 1508 in FIG. 15.

[0479] In some aspects, the energy consumptions of the plurality of power tools may comprise at least one of actual energy consumptions of the plurality of power tools received from the gateway or estimated energy consumptions of the plurality of power tools. For example, the energy consumptions may be actual energy consumptions received by the backend server 116 from the139WBD (US) 4911-1825-7051gateway 502 at 1506 or the energy consumptions may be estimated energy consumptions based on SKU data of the plurality of power tools.

[0480] In some aspects, presenting the GUI may include transmitting, to a user device, data that causes the user device to present the GUI on a display of the user device. For example, FIG. 15 at 1518 shows that the backend server 116 may transmit, to the user device, data that causes the user device to present the GUI on a display of the user device 120.

[0481] In some aspects, the plurality of power tools may comprise a first power tool of a first type and a second power tool of a second type, and the GUI may include a window depicting a first carbon dioxide equivalent emission of the first power tool of the first type and a second carbon dioxide equivalent emission of the second power tool of the second type. In an example, the aforementioned aspects may correspond to the emissions CChe by asset class section 1608 in FIG.16. In another example, the aforementioned aspects may correspond to the emissions CChe by asset class section 1702 in FIG. 17.

[0482] In some aspects, the GUI may depict a total carbon dioxide equivalent emission of the plurality of power tools for the period of time. In an example, the aforementioned aspects may correspond to the emissions CChe by asset class section 1608 in FIG. 16. In another example, the aforementioned aspects may correspond to the emissions CChe by asset class section 1702 in FIG.17. In yet another example, the aforementioned aspects may correspond to the carbon impact section 1602 and / or the impact equivalent section 1606.

[0483] In some aspects, the backend server may calculate a volume of gasoline that would be consumed if the plurality of power tools were gasoline-powered based on the indications of the runtimes and the energy consumptions of the plurality of power tools. For example, FIG. 15 at 1512 shows that the backend server 116 may calculate a volume of gasoline that would be 140WBD (US) 4911-1825-7051consumed if the plurality of power tools were gasoline-powered based on the indications of the runtimes and the energy consumptions of the plurality of power tools.

[0484] In some aspects, the backend server may calculate a carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered based on the volume of the gasoline, wherein the GUI may depict at least one of the volume of the gasoline or the carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered. For example, FIG. 15 at 1514 shows that the backend server 116 may calculate a carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered based on the volume of the gasoline, wherein the GUI may depict at least one of the volume of the gasoline or the carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered.

[0485] In some aspects, the plurality of power tools may comprise a first power tool associated with a first assignment of a first type and a second power tool associated with a second assignment of a second type, and the GUI may include a window depicting a first carbon dioxide equivalent emission for the first assignment of the first type and a second carbon dioxide equivalent emission for the second assignment of the second type. For example, the aforementioned aspects may correspond to the CChe emissions by assignment section 1604.

[0486] In some aspects, the first type and the second type may be included in a plurality of types of assignments comprising: a jobsite assignment, a project assignment, a work truck assignment, a job box assignment, or a warehouse assignment. For example, the aforementioned aspects may correspond to the CChe emissions by assignment section 1604.

[0487] In some aspects, the period of time may comprise at least one of months of a year, days of a week, or hours of a day (or some other time period), and wherein the GUI may depict a total carbon dioxide equivalent emission for at least one of: each month of the year, each day of a week,141WBD (US) 4911-1825-7051or each hour of a day (or some other time period). For example, the aforementioned aspects may correspond to the emissions CChe by asset class section 1608 in FIG. 16.

[0488] In some aspects, the backend server may receive, from a user device, a request for the carbon dioxide equivalent emissions of the plurality of power tools. For example, FIG. 15 at 1522 shows that the backend server 116 may receive, from the user device 120, a request for the carbon dioxide equivalent emissions of the plurality of power tools.

[0489] In some aspects, the backend server may transmit, to the user device based on the request, tabular data that includes the carbon dioxide equivalent emissions of the plurality of power tools. For example, FIG. 15 at 1524 shows that the backend server 116 may transmit, to the user device 120 based on the request, tabular data that includes the carbon dioxide equivalent emissions of the plurality of power tools.

[0490] In some aspects, the GUI may include a window that depicts a number of the plurality of power tools, a total runtime of the plurality of power tools, a total carbon dioxide equivalent emission for the plurality of power tools, and a volume of gasoline saved by using the plurality of power tools. For example, the aforementioned aspects may correspond to the carbon impact section 1602.

[0491] FIG. 52 is a flow diagram 5200 of a method performed by a backend server associated with a first organization for asset tracking on a jobsite in accordance with some aspects of the present disclosure. The method may be performed by processing logic that may include hardware (e.g., a processing device), software (e.g., instructions running / executing on a processing device), firmware (e.g., microcode), or a combination thereof. In some aspects, at least a portion of the method may be performed by the backend server 116, the computer system 5600, or a combination thereof.142WBD (US) 4911-1825-7051

[0492] The method illustrates example functions used by various embodiments. Although specific function blocks ("blocks") are disclosed in the method, such blocks are examples. That is, embodiments are well suited to performing various other blocks or variations of the blocks recited in the method. It is appreciated that the blocks in the method may be performed in an order different than presented, and that not all of the blocks in the method may be performed.

[0493] At block 5202, a backend server (associated with a first organization) generates a mobile assignment comprising an indication of a first gateway and an indication of a construction asset, wherein the first gateway is associated with a vehicle, and wherein the first gateway is associated with the first organization. For example, FIG. 18 at 1812 shows that the backend server 116 generates a mobile assignment comprising an indication of the first gateway 1804 and an indication of the construction asset 1802, wherein the first gateway 1804 is associated with the vehicle 1806, and wherein the first gateway 1804 is associated with the first organization.

[0494] At block 5204, the backend server receives, from a server associated with a second organization, an identifier for the construction asset and a location of the construction asset based on a detection of the construction asset by a second gateway associated with the second organization, wherein the location of the construction asset is outside of a range of the first gateway. For example, FIG. 18 at 1830 shows that the backend server 116 receives, from the server 1810 associated with a second organization, an identifier for the construction asset 1802 and a location of the construction asset 1802 based on a detection of the construction asset 1802 by the second gateway 1808 associated with the second organization, wherein the location of the construction asset is outside of a range of the first gateway 1804. In an example, the range of the first gateway 1804 may be the first range 1904 as depicted in the diagram 1900B.143WBD (US) 4911-1825-7051

[0495] At block 5206, the backend server updates an asset status of the construction asset in the mobile assignment based on the identifier for the construction asset and the location of the construction asset. For example, FIG. 18 at 1834 shows that the backend server 116 updates an asset status of the construction asset 1802 in the mobile assignment based on the identifier for the construction asset 1802 and the location of the construction asset 1802.

[0496] In some aspects, the backend server may determine that the first gateway has failed to detect the construction asset. For example, FIG. 18 at 1817 shows that the backend server 116 may determine that the first gateway 1804 has failed to detect the construction asset.

[0497] In some aspects, the backend server may transmit, to the server associated with the second organization and based on the determination, the identifier for the construction asset, wherein receiving the location of the construction asset from the server may be based on the transmitted identifier for the construction asset. For example, FIG. 18 at 1822 shows that the backend server 116 may transmit, to the server 1810 associated with the second organization and based on the determination at 1817, the identifier for the construction asset 1802, wherein receiving the location of the construction asset 1802 from the server 1810 at 1830 may be based on the transmitted identifier for the construction asset 1802.

[0498] In some aspects, determining that the first gateway has failed to detect the construction asset may comprise determining that the backend server has not received the location of the construction asset from the first gateway within a time interval. For example, determining that the first gateway has failed to detect the construction asset at 1817 may comprise determining that the backend server 116 has not received the location of the construction asset 1802 from the first gateway 1804 within a time interval.144WBD (US) 4911-1825-7051

[0499] In some aspects, determining that the first gateway has failed to detect the construction asset may comprise receiving, from the first gateway, a message indicating that the first gateway has failed to detect the construction asset. For example, determining that the first gateway has failed to detect the construction asset at 1817 may comprise receiving, from the first gateway 1804, a message indicating that the first gateway 1804 has failed to detect the construction asset 1802.

[0500] In some aspects, the first gateway may be disposed in the vehicle or integrated into the vehicle. For example, the first gateway 1804 may be disposed in the vehicle 1806 or integrated into the vehicle 1806.

[0501] In some aspects, the backend server may cause a GUI to be presented on a display of a user device, wherein the GUI may indicate the updated asset status. For example, FIG. 18 at 1836 and 1838 shows that the backend server 116 may cause a GUI to be presented on a display of a user device, wherein the GUI may indicate the updated asset status.

[0502] In some aspects, the second gateway may comprise at least one of a stationary gateway, a mobile gateway, a gateway integrated into a construction vehicle, or a public gateway. For example, the second gateway 1808 may comprise at least one of: a stationary gateway, a mobile gateway, a gateway integrated into a construction vehicle, or a public gateway.

[0503] In some aspects, the construction asset may comprise at least one of a tool or a battery pack. For example, the construction asset 1802 may comprise at least one of a tool (e g., the power tool 302, the power tool 402) or a battery pack (e.g., the battery pack 602).

[0504] In some aspects, the identifier for the construction asset may be associated with advertisement data emitted by the construction asset. For example, the advertisement data may be or include the advertisement signal 1908.145WBD (US) 4911-1825-7051

[0505] In some aspects, the vehicle, the first gateway, and the second gateway may be located on a jobsite. For example, FIG. 19A and FIG. 19B shows that the vehicle 1806, the first gateway 1804, and the second gateway 1808 may be located on the jobsite 1902.

[0506] In some aspects, the backend server may establish, prior to receiving the identifier for the construction asset and the location of the construction asset, a geofence boundary for the jobsite. For example FIG. 18 at 1814 shows that the backend server 116 may establish, prior to receiving the identifier for the construction asset 1802 and the location of the construction asset at 1830, a geofence boundary for the jobsite.

[0507] In some aspects, the backend server may compare the location of the construction asset received from the server to the geofence boundary for the jobsite, wherein updating the construction asset status of the construction asset in the mobile assignment may be based on the comparison. For example, FIG. 18 at 1832 shows that the backend server 116 may compare the location of the construction asset 1802 received from the server 1810 to the geofence boundary for the jobsite, wherein updating the construction asset status of the construction asset in the mobile assignment at 1834 may be based on the comparison.

[0508] In some aspects, updating the construction asset status of the construction asset based on the comparison may comprise updating the construction asset status to indicate that the construction asset is in a wrong location on the jobsite. For example, updating the construction asset status of the construction asset 1802 based on the comparison may comprise updating the construction asset status to indicate that the construction asset 1802 is in a wrong location on the jobsite.

[0509] In some aspects, updating the construction asset status of the construction asset based on the comparison may comprise updating the construction asset status to indicate that the 146WBD (US) 4911-1825-7051construction asset is not on the jobsite. For example, updating the construction asset status of the construction asset 1802 based on the comparison at 1834 may comprise updating the construction asset status to indicate that the construction asset 1802 is not on the jobsite.

[0510] In some aspects, receiving the identifier for the construction asset and the location of the construction asset may comprise receiving the identifier for the construction asset and the location of the construction asset via an API exposed by the backend server to the server. For example, receiving the identifier for the construction asset 1802 and the location of the construction asset 1802 may comprise receiving the identifier for the construction asset 1802 and the location of the construction asset 1802 via an API exposed by the backend server 116 to the server 1810.

[0511] FIG. 53 is a flow diagram 5300 of a method for asset and audit status management in accordance with some aspects of the present disclosure. The method may be performed by processing logic that may include hardware (e.g., a processing device), software (e.g., instructions running / executing on a processing device), firmware (e.g., microcode), or a combination thereof. In some aspects, at least a portion of the method may be performed by the backend server 116 (shown in FIG. 1), the processor 202 (shown in FIG. 2), the computer system 5600 (shown in FIG.56), the processing device 5602 (shown in FIG. 56), or a combination thereof.

[0512] The method illustrates example functions used by various embodiments. Although specific function blocks ("blocks") are disclosed in the method, such blocks are examples. That is, embodiments are well suited to performing various other blocks or variations of the blocks recited in the method. It is appreciated that the blocks in the method may be performed in an order different than presented, and that not all of the blocks in the method may be performed.

[0513] At block 5302, processing logic generates a plurality of assignments, wherein the plurality of assignments includes an assignment of a central device to a first location in a jobsite, where the 147WBD (US) 4911-1825-7051plurality of assignments further includes assignments for assets in the jobsite, the assignments for the assets including locations of the assets in the jobsite and audit frequencies for the assets. In an example, generating the plurality of assignments may correspond to 2704 in FIG. 27. In an example, the plurality of assignments may be or include the first assignments 210. In an example, the central device may be or include the first central device 114 and the jobsite may be or include the first jobsite 212. In another example, the jobsite may be the first jobsite 802. In an example, the assets may be or include the first asset 102 and / or the Ath asset 104. In an example, the audit frequencies may correspond to the first audit frequency 218.

[0514] At block 5304, the processing logic receives, from the central device located at the first location, audit statuses for the assets, the audit statuses being based on signals transmitted by peripheral devices associated with the assets, the signals being sensed by the central device. In an example, receiving the audit statuses may correspond to 2712 in FIG. 27. In an example, the audit statuses may be or include the first audit status 220 and / or the Ath audit status 222. In an example, the signals may be or include the first signal 110 and / or the Ath signal 112. In an example, the peripheral devices may be or include the first peripheral device 106 and / or the Ath peripheral device 108.

[0515] At block 5306, the processing logic determines, based on the assignments for the assets, asset statuses for the assets. In an example, the asset statuses may be or include the first asset status 214 and / or the Ath asset status 216. In an example, determining the asset statuses may correspond to 2704 and / or 2712 in FIG. 27.

[0516] At block 5308, the processing logic provides a GUI that depicts graphical information about at least one of the audit statuses for the assets or the asset statuses for the assets. In an example, providing the GUI may correspond to 2714 in FIG. 27. In an example, the GUI may be 148WBD (US) 4911-1825-7051or include the GUI 712, the asset statuses may be or include the asset statuses 728, and the audit statuses may be or include the audit statuses 730. In an example, the GUI may be or include the GUI depicted in FIG. 29, the asset statuses may be or include the asset statuses 2902, and the audit statuses may be or include the audit statuses 2904. In another...

Claims

CLAIMSWhat is claimed is:

1. A method performed by a backend server for asset onboarding, comprising:receiving, from a gateway, an identifier for a user account and identifiers for a plurality of construction assets detected by the gateway within a range of the gateway, wherein the user account is maintained by the backend server;determining that at least one construction asset in the plurality of construction assets is not associated with the user account based on the identifier for the user account and the identifiers for the plurality of construction assets; andassociating an identifier for the at least one construction asset with the user account based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the user account.

2. The method of claim 1, further comprising:determining that the at least one construction asset in the plurality of construction assets is not associated with additional user accounts maintained by the backend server based on the identifiers for the plurality of construction assets, wherein associating the identifier for the at least one construction asset with the user account is additionally based on the determination that the at least one construction asset in the plurality of construction assets is not associated with the additional user accounts.

3. The method of claim 1, further comprising:191WBD (US) 4911-1825-7051receiving, from a user device, information pertaining to the at least one construction asset subsequent to associating the at least one construction asset with the user account; and associating the information pertaining to the at least one construction asset with the identifier for the at least one construction asset associated with the user account.

4. The method of claim 3, further comprising:receiving, from the user device and prior to receiving the information pertaining to the at least one construction asset, a request for a graphical user interface (GUI) for entering the information pertaining to the at least one construction asset; andcausing the GUI for entering the information pertaining to the at least one construction asset to be presented on the user device.

5. The method of claim 1, further comprising:executing a search over a log of construction asset information based on the identifier for the at least one construction asset;identifying information pertaining to the at least one construction asset based on search results for the search; andassociating the information pertaining to the at least one construction asset with the identifier for the at least one construction asset associated with the user account.

6. The method of claim 1, wherein the identifier for the at least one construction asset comprises a medium access control (MAC) address.192WBD (US) 4911-1825-70517. The method of claim 1, wherein the plurality of construction assets comprises at least one of tools or battery packs.

8. The method of claim 1, wherein the gateway comprises a smartphone.

9. The method of claim 1, further comprising:transmitting, to a user device, an indication that the at least one construction asset has been associated with the user account.

10. A backend server, comprising:a processor; andmemory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of claims 1-9.

11. An apparatus comprising means for implementing a method as in any of claims 1-9.

12. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of claims 1-9.

13. A computer program product for implementing a method as in any of claims 1 -9.

14. A method performed by a gateway for asset onboarding, comprising:performing, via a wireless controller of the gateway, a scan;193WBD (US) 4911-1825-7051obtaining identifiers for a plurality of construction assets within a range of the gateway based on scan results for the scan, wherein at least one construction asset in the plurality of construction assets is not associated with a user account maintained by a backend server; and transmitting, to the backend server, an identifier for the user account and the identifiers for the plurality of construction assets.

15. The method of claim 14, further comprising:receiving, from a user device, a command to perform the scan, wherein performing the scan is based on the command.

16. The method of claim 14, wherein the gateway comprises a smartphone, the method further comprising:receiving user input indicative of the scan, wherein performing the scan is based on the user input.

17. The method of claim 14, wherein performing the scan comprises receiving a plurality of advertisement signals emitted by the plurality of construction assets, wherein the plurality of advertisement signals include the identifiers for the plurality of construction assets.

18. The method of claim 14, further comprising:receiving, from the backend server, an indication that the at least one construction asset has been associated with the user account.194WBD (US) 4911-1825-705119. The method of claim 14, wherein the gateway comprises a smartphone, the method further comprising:receiving, as user input, information pertaining to the at least one construction asset; and transmitting, to the backend server, the information pertaining to the at least one construction asset for association with the at least one construction asset in the user account.

20. The method of claim 19, further comprising:transmitting, to the backend server, a request for a graphical user interface (GUI) for entering the information pertaining to the at least one construction asset;receiving, from the backend server and based on the request, graphical data; and presenting the GUI based on the graphical data, wherein the GUI receives the information pertaining to the at least one construction asset.

21. The method of claim 14, wherein the identifiers for the plurality of construction assets comprise medium access control (MAC) addresses.

22. The method of claim 14, wherein the plurality of construction assets comprises at least one of tools or battery packs.

23. A gateway comprising:a wireless controller;a processor; and195WBD (US) 4911-1825-7051memory storing instructions that, when executed by the processor, cause the processor to implement the method as in any of claims 14-22.

24. An apparatus comprising means for implementing a method as in any of claims 14-22.

25. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of claims 14-22.

26. A computer program product for implementing a method as in any of claims 14-22.

27. A method for tracking power tool emissions, comprising:receiving, from a gateway, indications of runtimes of a plurality of power tools that are powered via electricity from a power grid and an indication of a location of the plurality of power tools;obtaining, based on the indication of the location of the plurality of power tools, an estimate of emissions associated with the power grid;calculating a carbon dioxide equivalent emissions of the plurality of power tools over a period of time based on the indications of the runtimes, energy consumptions of the plurality of power tools, and the estimate of the emissions associated with the power grid; and presenting a graphical user interface (GUI) that depicts graphical information pertaining to the carbon dioxide equivalent emissions of the plurality of power tools.196WBD (US) 4911-1825-705128. The method of claim 27, wherein obtaining the estimate of the emissions associated with the power grid comprises:determining, based on the location of the plurality of power tools, a geographic region that encompasses the location of the plurality of power tools;transmitting, to a power profde service, an indication of the geographic region; and receiving, from the power profde service, the estimate of the emissions associated with the power grid based on the indication of the geographic region.

29. The method of claim 27, wherein the energy consumptions of the plurality of power tools comprise at least one of actual energy consumptions of the plurality of power tools received from the gateway or estimated energy consumptions of the plurality of power tools.

30. The method of claim 27, wherein presenting the GUI comprises:transmitting, to a user device, data that causes the user device to present the GUI on a display of the user device.

31. The method of claim 27, wherein the plurality of power tools comprises a first power tool of a first type and a second power tool of a second type, and wherein the GUI includes a window depicting a first carbon dioxide equivalent emission of the first power tool of the first type and a second carbon dioxide equivalent emission of the second power tool of the second type.

32. The method of claim 27, wherein the GUI depicts a total carbon dioxide equivalent emission of the plurality of power tools for the period of time.197WBD (US) 4911-1825-705133. The method of claim 27, further comprising:calculating a volume of gasoline that would be consumed if the plurality of power tools were gasoline-powered based on the indications of the runtimes and the energy consumptions of the plurality of power tools; andcalculating a carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered based on the volume of the gasoline, wherein the GUI depicts at least one of the volume of the gasoline or the carbon dioxide equivalent emission if the plurality of power tools were gasoline-powered.

34. The method of claim 27, wherein the plurality of power tools comprises a first power tool associated with a first assignment of a first type and a second power tool associated with a second assignment of a second type, and wherein the GUI includes a window depicting a first carbon dioxide equivalent emission for the first assignment of the first type and a second carbon dioxide equivalent emission for the second assignment of the second type.

35. The method of claim 34, wherein the first type and the second type are included in a plurality of types of assignments comprising:a jobsite assignment;a project assignment;a work truck assignment;a job box assignment; ora warehouse assignment.198WBD (US) 4911-1825-705136. The method of claim 27, wherein the period of time comprises at least one of: months of a year, days of a week, or hours of a day, and wherein the GUI depicts a total carbon dioxide equivalent emission for at least one of: each month of the year, each day of the week, or each hour of the day.

37. The method of claim 27, further comprising:receiving, from a user device, a request for the carbon dioxide equivalent emissions of the plurality of power tools; andtransmitting, to the user device based on the request, tabular data that includes the carbon dioxide equivalent emissions of the plurality of power tools.

38. The method of claim 27, wherein the GUI includes a window that depicts:a number of the plurality of power tools;a total runtime of the plurality of power tools;a total carbon dioxide equivalent emission for the plurality of power tools;a volume of gasoline saved by using the plurality of power tools; andcost savings from using the plurality of power tools that are powered via the electricity from the power grid.

39. A computing system, comprising:a processor; and199WBD (US) 4911-1825-7051memory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of claims 27-38.

40. An apparatus comprising means for implementing a method as in any of claims 27-38.

41. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of claims 27-38.

42. A computer program product for implementing a method as in any of claims 27-38.

43. A method performed by a backend server associated with a first organization for asset tracking on a jobsite, comprising:generating a mobile assignment comprising an indication of a first gateway and an indication of a construction asset, wherein the first gateway is associated with a vehicle, and wherein the first gateway is associated with the first organization;receiving, from a server associated with a second organization, an identifier for the construction asset and a location of the construction asset based on a detection of the construction asset by a second gateway associated with the second organization, wherein the location of the construction asset is outside of a range of the first gateway; andupdating an asset status of the construction asset in the mobile assignment based on the identifier for the construction asset and the location of the construction asset.

44. The method of claim 43, further comprising:200WBD (US) 4911-1825-7051determining that the first gateway has failed to detect the construction asset; and transmitting, to the server associated with the second organization and based on the determination, the identifier for the construction asset, wherein receiving the location of the construction asset from the server is based on the transmitted identifier for the construction asset.

45. The method of claim 44, wherein determining that the first gateway has failed to detect the construction asset comprises determining that the backend server has not received the location of the construction asset from the first gateway within a time interval.

46. The method of claim 44, wherein determining that the first gateway has failed to detect the construction asset comprises receiving, from the first gateway, a message indicating that the first gateway has failed to detect the construction asset.

47. The method of claim 43, where the first gateway is disposed in the vehicle or integrated into the vehicle.

48. The method of claim 43, further comprising:causing a graphical user interface (GUI) to be presented on a display of a user device, wherein the GUI indicates the updated asset status.

49. The method of claim 43, wherein the second gateway comprises at least one of:a stationary gateway;a mobile gateway;201WBD (US) 4911-1825-7051a gateway integrated into a construction vehicle; ora public gateway.

50. The method of claim 43, wherein the construction asset comprises at least one of a tool or a battery pack.

51. The method of claim 43, wherein the identifier for the construction asset is associated with advertisement data emitted by the construction asset.

52. The method of claim 43, wherein the vehicle, the first gateway, and the second gateway are located on the jobsite.

53. The method of claim 43, further comprising:establishing, prior to receiving the identifier for the construction asset and the location of the construction asset, a geofence boundary for the jobsite; andcomparing the location of the construction asset received from the server to the geofence boundary for the jobsite, wherein updating the construction asset status of the construction asset in the mobile assignment is based on the comparison.

54. The method of claim 53, wherein updating the construction asset status of the construction asset based on the comparison comprises updating the construction asset status to indicate that the construction asset is in a wrong location on the jobsite.202WBD (US) 4911-1825-705155. The method of claim 53, wherein updating the construction asset status of the construction asset based on the comparison comprises updating the construction asset status to indicate that the construction asset is not on the jobsite.

56. The method of claim 43, wherein receiving the identifier for the construction asset and the location of the construction asset comprises receiving the identifier for the construction asset and the location of the construction asset via an application programming interface (API) exposed by the backend server to the server.

57. A backend server, comprising:a processor; andmemory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of claims 43-56.

58. An apparatus comprising means for implementing a method as in any of claims 43-56.

59. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of claims 43-56.

60. A computer program product for implementing a method as in any of claims 43-56.

61. A method, comprising:203WBD (US) 4911-1825-7051generating a plurality of assignments, wherein the plurality of assignments includes an assignment of a central device to a first location in a jobsite, wherein the plurality of assignments further includes assignments for assets in the jobsite, the assignments for the assets including locations of the assets in the jobsite and audit frequencies for audits of the assets;receiving, from the central device located at the first location, audit statuses for the assets, the audit statuses being based on signals transmitted by peripheral devices associated with the assets, the signals being sensed by the central device;determining, based on the assignments for the assets, asset statuses for the assets; and providing a graphical user interface (GUI) that depicts graphical information about at least one of the audit statuses for the assets or the asset statuses for the assets.

62. The method of claim 61, wherein the asset statuses include at least one of:a first number of the assets that are available for deployment,a second number of the assets that are deployed, ora third number of the assets that are missing or lost based on non-receipt of a signal by the central device.

63. The method of claim 61, wherein the audit statuses include at least one of:a first number of the assets that have been sensed by the central device during an audit within the audit frequencies,a second number of the assets that require audit based on the assignments,204WBD (US) 4911-1825-7051a third number of the assets that are overdue for the audit, the third number of the assets being based on non-receipt of a signal by the central device during the audit within the audit frequencies, ora fourth number of the assets that are in a wrong location, the fourth number of the assets being based on a receipt of the signal by a second central device located at a second location.

64. The method of claim 61, wherein providing the GUI comprises transmitting, to a user device and over a network, data that causes the user device to present the GUI on a display of the user device.

65. The method of claim 61, wherein the GUI depicts a plurality of selectable categories associated with the asset statuses, wherein each of the plurality of selectable categories, when selected, causes information to be presented within the GUI pertaining to a subset of the assets belonging to a selectable category in the plurality of selectable categories, and wherein the plurality of selectable categories includes at least one of:available assets,deployed assets,missing assets,service needed assets,out for service assets, orlost assets.205WBD (US) 4911-1825-705166. The method of claim 61, wherein the GUI depicts a plurality of selectable categories associated with the audit statuses, wherein each of the plurality of selectable categories, when selected, causes information to be presented within the GUI pertaining to a subset of the assets belonging to a selectable category in the plurality of selectable categories, and wherein the plurality of selectable categories includes at least one of:audit assets,needs audit assets,overdue assets, orwrong location assets.

67. The method of claim 66, wherein the GUI further comprises a chart that depicts a first percentage of the assets corresponding to the audit assets, a second percentage of the assets corresponding to the needs audit assets, a third percentage of the assets corresponding to the overdue assets, and a fourth percentage of the asset corresponding to the wrong location assets.

68. The method of claim 61, further comprising:obtaining, from a user device, data indicative of the plurality of assignments, wherein generating the plurality of assignments is based on the data indicative of the plurality of assignments.

69. The method of claim 61, wherein the central device comprises at least one of gateway or a user device.206WBD (US) 4911-1825-705170. The method of claim 61, wherein the plurality of assignments indicates that the assets are assigned to the central device.

71. The method of claim 61, wherein the plurality of assignments is associated with a plurality of user accounts stored in a memory.

72. The method of claim 61, wherein the assignment of the central device to the first location in the jobsite is a first assignment of a first central device to the first location in a first jobsite, the assignments for assets in the jobsite are first assignments for first assets in the first jobsite, the assignments for the assets including locations of the assets in the jobsite and audit frequencies for audits of the assets are first locations of the first assets in the first jobsite and first audit frequencies for audits of the first assets in the first jobsite, audit statuses for the assets based on signals transmitted by peripheral devices associated with the assets are first audit statuses for the first assets based on first signals transmitted by first peripheral devices associated with the first assets, asset statuses for the assets are first asset statuses for the first assets the graphical information is first graphical information, whereinthe plurality of assignments includes a second assignment of a second central device to a second location in a second job site, and wherein the plurality of assignments further includes second assignments for second assets in the second job site, the second assignments for the second assets including second locations of the second assets in the second jobsite and second audit frequencies for audits of the second assets, the method further comprising:receiving, from the second central device located at the second location, second audit statuses for the second assets, the second audit statuses being based on second signals transmitted207WBD (US) 4911-1825-7051by second peripheral devices associated with the second assets, the second signals being sensed by the second central device; anddetermining, based on the second assignments for the second assets, second asset statuses for the second assets, wherein the GUI further depicts second graphical information about at least one of the second audit statuses for the second assets or the second asset statuses for the second assets.

73. The method of claim 72, further comprising:determining, based on the second audit statuses, that the second central device received a signal transmitted by a first asset associated with the first assignments corresponding to the first central device;determining that the first assignments and the second assignments are both associated with a same user account; andtransmitting, to a user device and over a network, a message comprising at least one of:a first indication that the first asset has been sensed within the second job site, or a second indication of an option to reassign the first asset to the second assignments.

74. The method of claim 73, further comprising:receiving, from the user device and over the network, a response to the message, the response indicating that the first asset is to be reassigned to the second assignments; and reassigning, based on the response, the first asset from the first assignments to the second assignments.208WBD (US) 4911-1825-705175. The method of claim 61, wherein the assets comprise at least one of power tools, power tool accessories, construction tools, or construction materials.

76. The method of claim 61, wherein the signals are periodically transmitted by the peripheral devices.

77. The method of claim 61, wherein the peripheral devices comprise wireless communication devices.

78. The method of claim 61, wherein the central device is associated with a sensing range, and wherein the central device senses the signals when the assets are within the sensing range associated with the central device.

79. A backend server, comprising:a processor; andmemory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of claims 61-78.

80. An apparatus comprising means for implementing a method as in any of claims 61-78.

81. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of claims 61-78.209WBD (US) 4911-1825-705182. A computer program product for implementing a method as in any of claims 61-78.

83. A method, comprising:obtaining an audit status for each of a plurality of construction assets associated with a user account;providing a graphical user interface (GUI) depicting a first view of a map indicating geographic locations of each of the plurality of construction assets; andresponsive to receiving an indication of a selection of a location of a jobsite on the first view of the map, adjusting the GUI to depict a second view of the map indicating a subset of the plurality of construction assets associated with the jobsite and audit statuses for each construction asset of the subset, wherein the second view is a zoomed-in version of the first view.

84. The method of claim 83, further comprising:receiving an indication of a selection of a first construction asset in the subset; and responsive to receiving the indication of the selection of the first construction asset, providing, within the GUI and overlaid on the map, a first window indicating an identifier for the first construction asset and a first audit status of the first construction asset.

85. The method of claim 84, wherein the first audit status comprises:an indication that the first construction asset is audited, requires an audit, is overdue, or is in a wrong location,a time of a most recent audit of the first construction asset, and210WBD (US) 4911-1825-7051an identifier for a gateway that performed the most recent audit of the first construction asset.

86. The method of claim 84, wherein the first audit status indicates that the first construction asset is in a wrong location, wherein the first construction asset is assigned to a first assignment, the method further comprising:receiving an indication of a selection of a transfer button displayed within the first window; responsive to receiving the indication of the selection of the transfer button displayed within the first window, providing within the GUI and overlaid on the map, a second window including fields for transferring the first construction asset from the first assignment to a second assignment; andresponsive to obtaining input data for the fields, transferring the first construction asset from the first assignment to the second assignment based on the input data for the fields.

87. The method of claim 86, wherein the input data for the fields comprises at least one of:an identifier for the second assignment,a date for transferring the first construction asset from the first assignment to the second assignment,an asset status for the first construction asset,a person responsible for the first construction asset, ornotes pertaining to the first construction asset.211WBD (US) 4911-1825-705188. The method of claim 83, wherein the GUI further includes a window, displayed proximate to the map, indicating the audit status for each of the plurality of construction assets when the map is depicted in the first view, and wherein the window indicates a first audit status for each construction asset of the subset when the map is depicted in the second view.

89. The method of claim 83, wherein the GUI includes at least one of: an audit status type filter menu, an assignment filter menu, or a responsible person filter menu, the method further comprising:receiving an indication of a selection of at least one of:an audit status type from amongst a plurality of audit status types displayed within the audit status type filter menu,an assignment from amongst a plurality of assignments displayed within the assignment filter menu, ora responsible person from amongst a plurality of responsible persons displayed within the responsible person filter menu; andupdating the GUI to remove a construction asset from the map that is not associated with the at least one of the audit status type, the assignment, or the responsible person.

90. The method of claim 89, wherein updating the GUI to remove the construction asset from the map occurs responsive to adjusting the GUI to depict the second view of the map.

91. The method of claim 83, wherein the jobsite corresponds to an assignment, and wherein the GUI further depicts a geographic boundary associated with the assignment.212WBD (US) 4911-1825-705192. The method of claim 83, wherein the plurality of construction assets includes at least one of:a power tool,a power tool accessory,a battery pack,a construction tool, ora construction material.

93. The method of claim 83, wherein providing the GUI comprises transmitting the GUI over a network to a user device.

94. The method of claim 83, wherein obtaining the audit status for each of the plurality of construction assets comprises receiving the audit statuses over a network from a gateway associated with the jobsite.

95. A backend server, comprising:a processor; andmemory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of claims 83-94.

96. An apparatus comprising means for implementing a method as in any of claims 83-94.213WBD (US) 4911-1825-705197. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of claims 83-94.

98. A computer program product for implementing a method as in any of claims 83-94.

99. A method, comprising:receiving, from a user device, an indication of a construction asset category and a service plan for the construction asset category for a user account;applying, for the user account, the service plan to each of a plurality of construction assets that belong to the construction asset category;determining, based on the service plan, that a construction asset in the plurality of construction assets on a jobsite is due for service; andtransmitting, to the user device, a notification indicating that the construction asset is due for the service based on the determination that the construction asset is due for the service.

100. The method of claim 99, wherein the construction asset comprises a plurality of components that operate in conjunction with one another to provide a functionality, wherein the construction asset category and the service plan pertain to a component in the plurality of components, and wherein the notification indicates that the component is due for the service.

101. The method of claim 99, further comprising:providing, to the user device, a graphical user interface (GUI) that includes a first field for the construction asset category and a second field for the service plan, wherein receiving the214WBD (US) 4911-1825-7051indication of the construction asset category and the service plan for the construction asset category is based on input set forth to the first field and the second field.

102. The method of claim 99, wherein the service plan indicates a time period, wherein the service plan is applied at a time instance, wherein determining that the construction asset is due for the service includes determining that a difference between a current time instance and the time instance is greater than or equal to the time period.

103. The method of claim 99, wherein the service plan indicates a threshold operational runtime, the method further comprising:receiving, from a gateway, an indication of an operational runtime of the construction asset, wherein determining that the construction asset is due for the service includes determining that the operational runtime of the construction asset is greater than the threshold operational runtime.

104. The method of claim 99, wherein the service plan indicates a time period, wherein the service plan is applied at a first time instance, wherein determining that the construction asset is due for the service includes:identifying a second time instance associated with a last service of the construction asset; anddetermining that a difference between the first time instance and the second time instance is greater than the time period.

105. The method of claim 99, further comprising:215WBD (US) 4911-1825-7051receiving, from the user device, an indication of new construction asset that is to be associated with the user account as part of an onboarding process;determining, during the onboarding process, that the new construction asset belongs to the construction asset category; andapplying, during the onboarding process, the service plan to the new construction asset based on the determination that the new construction asset belongs to the construction asset category.

106. The method of claim 99, wherein applying the service plan to each of the plurality of construction assets includes associating an identifier for each of the plurality of construction assets with the service plan.

107. The method of claim 99, wherein receiving the indication of the construction asset category and the service plan from the user device includes receiving the indication of the construction asset category and the service plan from a first user device, wherein transmitting the notification to the user device includes transmitting the notification to a second user device that is different from the first user device.

108. The method of claim 99, wherein the plurality of construction assets includes at least one of:a power tool,a power tool accessory,a battery pack,216WBD (US) 4911-1825-7051a construction tool, ora construction material.

109. The method of claim 99, further comprising:receiving, from the user device, an identifier of a service provider associated with the service plan, wherein the notification includes the identifier of the service provider.

110. The method of claim 99, further comprising:receiving, from the user device, a date at which the service was performed on the construction asset; andstoring the date as a last competed service date for the construction asset.

111. A backend server, comprising:a processor; andmemory storing instructions that, when executed by the processor, cause the processor to implement a method as in any of claims 99-110.

112. An apparatus comprising means for implementing a method as in any of claims 99-110.

113. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to implement a method as in any of claims 99-110.

114. A computer program product for implementing a method as in any of claims 99-110.217WBD (US) 4911-1825-7051

Images