Patent Description:
In a mass excavation project, a large amount of excavated material or mass is normally loaded onto transporting assets, e.g. trucks or haulers, and loaded out from the site of a mass excavation. The load-out material is then typically transported by the transporting assets towards one or more destination sites, such as, for example, landfills, dump sites or specific depots. Landfills or dump sites are normally for storage, e.g. to fill out land, while specific depots may be used for necessary further processing of the load-out material. For example, load-out material that may comprise hazardous and/or contaminated material may need to be transported to such specific depots to be processed in a specific manner; this, in order to ensure compliance with certain laws, regulations or environmental requirements when handling these type of materials.

Today, however, when managing mass excavation projects, the transporting assets may be directed to the same or different destination sites without coordination. This may results in increased environmental impacts and higher cost in handling the load-out material for a mass excavation project.

<CIT> describes a device and management platform on site for managing material handling productivity.

According to a first aspect of the examples herein, a method performed by a network system for enabling management of a mass excavation project, wherein the mass excavation project is associated with one or more transporting assets and one or more load destination sites is described. Each destination site is associated with a maximum material weight receiving capacity. The method comprise obtaining, from a user device associated with a transporting asset, a first information indicating that the transporting asset has been loaded with excavated material. Also, the method comprise providing, to the user device associated with the transporting asset, a load receipt based on the obtained first information, whereby the load receipt is associated with a load destination site for depositing the excavated material. Furthermore, the method comprise obtaining, from the user device associated with the transporting asset, a second information indicating that the transporting asset has off-loaded the excavated material at the load destination site and the weight of the excavated material. The method also comprise determining a remaining material weight receiving capacity of the load destination site based on the obtained weight of the excavated material and the maximum material weight receiving capacity of the load destination site.

The first aspect of the disclosure may seek to enable an improved management of a mass excavation project. A technical benefit may include improved utilization of transporting assets associated with a mass excavation project. This may further lead to reduced environmental impact and/or lower cost associated with the mass excavation project.

In some examples, the method may further comprise providing, to user devices associated with the one or more transporting assets and/or user devices associated with the mass excavation project, information indicating the determined remaining material weight receiving capacity of the load destination site. A technical benefit may include that a driver of a transporting asset carrying a load out associated with the mass excavation project may be given an indication of which destination site is most advantageous to deposit the excavated material. Additionally, foremen, truck dispatchers, site managers, machine operators using other user devices may also be provided with this information.

In some examples, the method may further comprise disabling associations of load receipts to a load destination site when the remaining material weight receiving capacity of the load destination site falls below a predetermined threshold level. A technical benefit may include that a load destination site that may be closed, is about to close or have already exceeded its maximum capacity for the current work shift may be made unavailable for association with a load receipt. This means that a transporting assets may no longer be directed towards this particular destination site.

In some examples, the method may further comprise providing, to the user device associated with the transporting asset, a delivery receipt based on the obtained second information. A technical benefit may include that a destination site that the driver of the transporting asset is notified of the fact that the load has been centrally registered.

In some examples, the obtained weight of the excavated material is a crowned or verified weight obtained at the load destination site by the user device associated with the transporting asset. A technical benefit may include that using a crowned or verified weight may be that more accurate weight levels may be achieved, thus increasing the accuracy of the determined remaining material weight receiving capacity of a load destination site.

According to a second aspect of the examples herein, a network system for enabling management of a mass excavation project, wherein the mass excavation project is associated with one or more transporting assets and one or more load destination sites is described. Each destination site is associated with a maximum material weight receiving capacity. The network system comprises a processing circuitry and a memory. The processing circuitry is configured to obtain, from a user device associated with a transporting asset, a first information indicating that the transporting asset has been loaded with excavated material, provide, to the user device associated with the transporting asset, a load receipt based on the obtained first information, whereby the load receipt is associated with a load destination site for depositing the excavated material, obtain, from the user device associated with the transporting asset, a second information indicating that the transporting asset has off-loaded the excavated material at the load destination site and the weight of the excavated material, and determine a remaining material weight receiving capacity of the load destination site based on the obtained weight of the excavated material and the maximum material weight receiving capacity of the load destination site.

In some examples, the processing circuitry may further be configured to provide, to user devices associated with the one or more transporting assets, information indicating the determined remaining material weight receiving capacity of the load destination site. In some examples, the processing circuitry may further be configured to disable associations of load receipts to a load destination site when the remaining material weight receiving capacity of the load destination site falls below a predetermined threshold level. In some examples, the processing circuitry may further be configured to provide, to the user device associated with the transporting asset, a delivery receipt based on the obtained second information. Effects and advantages of this second aspect is to a large extent analogous to those described above in connection with the first aspect.

According to a third aspect of the examples herein, a method performed by a user device associated with a transporting asset for enabling management of a mass excavation project is described. The method comprise providing, to a network system, a first information indicating that the transporting asset has been loaded with excavated material. The method also comprise obtaining, from the network system, a load receipt based on the provided first information, whereby the load receipt is associated with a load destination site for depositing the excavated material. The method further comprise receiving, at the load destination site associated with the load receipt, information indicating the weight of the excavated material. Furthermore, the method comprise providing, to a network system, a second information indicating that the transporting asset has off-loaded the excavated material at the load destination site and the received weight of the excavated material. Effects and advantages of this third aspect is to a large extent analogous to those described above in connection with the first aspect.

In some examples, the method may further comprise triggering an alert in the user device when the remaining material weight receiving capacity of a load destination site associated with an obtained the load receipt falls below a preconfigured threshold level. A technical benefit may include that a driver of a transporting asset carrying a load out associated with the mass excavation project may be given an indication that the destination site towards which it is heading may be closed, is about to close or have already exceeded its maximum capacity for the current work shift and therefore in unavailable. This means that the destination site may not be available for the transporting asset to make its deposit and that the transporting asset should proceed to another destination site for depositing its loaded excavated material.

According to a fourth aspect of the examples herein, a user device associated with a transporting asset for enabling management of a mass excavation project is described. The user device comprise a processing circuitry and a memory. The processing circuitry is configured to provide, to a network system, a first information indicating that the transporting asset has been loaded with excavated material, obtain, from the network system, a load receipt based on the provided first information, whereby the load receipt is associated with a load destination site for depositing the excavated material, receiving, at the load destination site associated with the load receipt, information indicating the weight of the excavated material, provide, to a network system, a second information indicating that the transporting asset has off-loaded the excavated material at the load destination site and the received weight of the excavated material.

In some examples, the processing circuitry may further be configured to trigger an alert in the user device when the remaining material weight receiving capacity of a load destination site associated with an obtained the load receipt falls below a preconfigured threshold level. Effects and advantages of this fourth aspect is to a large extent analogous to those described above in connection with the third aspect.

According to a fifth aspect of the examples herein, a vehicle comprising a user device as described above. According to a sixth aspect of the examples herein, a computer program product comprising program code means for performing the steps of the methods described above when said program is run on a processing circuitry of a network system or a processing circuitry of a user device, respectively, is described. According to a seventh aspect of the examples herein, a non-transitory computer-readable storage medium comprising instructions, which when executed on a processing circuitry of a network system or on a processing circuitry of a user device, cause the processing circuitry to perform the methods described above is described. Effects and advantages of these fifth, sixth and seventh aspects are to a large extent analogous to those described above in connection with the first aspect.

<FIG> illustrates an example of a network system <NUM> and a user device <NUM> for enabling management of a mass excavation project according to examples described herein. Here, it should be noted that the network system <NUM> may be implemented by one or more centrally located and/or distributed network units, such as, e.g. online data processing server(s), configured to manage mass excavation projects. The network system <NUM> and the one or more centrally located and/or distributed network units may also form part of a cloud service configured to manage mass excavation projects. The network system <NUM> may be connected to and configured to wirelessly communicate with the user device <NUM> via a wireless communications network <NUM>, wherein the wireless communications network <NUM> may comprise one or more radio base stations or access points <NUM>, <NUM> for enabling a wireless communication between the network system <NUM> and the user device <NUM>. The user device <NUM> may be operated by a driver <NUM> of a transporting asset <NUM> via a user interface 141a. The user device <NUM> may, for example, be a wireless device, such as, a mobile, cellular or smart phone or tablet, being capable of wireless communications with the network system <NUM> via the wireless communications network <NUM>. Optionally, the user device <NUM> may be embedded in on-board communication system of the transporting asset <NUM>, thereby being capable of wireless communications with the network system <NUM> via the wireless communications network <NUM>. The transporting asset <NUM> may be any form of vehicle arranged to carry and transport excavated material from a site of a mass excavation project to a destination site, such as, e.g. a truck, a hauler or a load carrier.

<FIG> shows possible routes of different transporting assets <NUM>, <NUM>, <NUM> from a site S of a mass excavation project to destination sites T<NUM>, T<NUM>. Although only three transporting assets and two destination sites are shown associated with the mass excavation project in <FIG> for the sake of simplicity, it should be noted that a mass excavation project may be associated with any number or plurality of different transporting assets and/or any number or plurality of different destination sites.

As part of developing the examples described herein, it has been realized that as an excavator or loader at a site S of a mass excavation project has finished loading excavated material onto a transporting asset, e.g. transporting asset <NUM>, a digital load receipt for the transporting asset <NUM> is normally generated by the network system <NUM> and sent out to the user device <NUM>. This may, for example, be performed in response to receiving information from the user device <NUM>, or e.g. from a load check-out system implemented at the site S of the mass excavation project, indicating that the transporting asset <NUM> has been loaded with excavated material and is about to transport the excavated material away from the site S of the mass excavation project. Upon generating the digital load receipt, the network system <NUM> may connect each digital load receipt with one of the available destination sites T<NUM>, T<NUM>, which designates and directs the driver <NUM> of the transporting assets to one of the available destination sites T<NUM>, T<NUM>. However, this is conventionally performed by the network system <NUM> without any awareness or consideration of the current capabilities of the destination sites T<NUM>, T<NUM>.

Here, each of the available different sites T<NUM>, T<NUM> may be associated with a maximum material weight receiving capacity. This means, for example, that each of the landfills, dump sites or specific depots may have specific limits for how much material or mass they are able to receive and/or process during a normal work shift. This may cause problems when, for example, a mass excavation project loads out a large amount of materials from a mass excavation site S onto several different transporting assets <NUM>, <NUM>, <NUM> and sends them to a destination site T<NUM>, T<NUM> that is closed or cant receive any more material for further processing (e.g. the destination site has reached its maximum receiving capacity for the current work shift). This means that the transporting assets <NUM>, <NUM>, <NUM> may have to be re-routed to other one of the available different sites T<NUM>, T<NUM> to be off-loaded, which will lead to a higher environmental impact for the transportation and likely also higher costs. There is also an additional risk that the transporting assets <NUM>, <NUM>, <NUM> will not be able to be unloaded until the next day if no other suitable destination sites may be found. In this case, for example, if one or more of the transporting assets <NUM>, <NUM>, <NUM> are loaded with wet clay and re-routed late in the afternoon to other destination sites, but are not able to be unloaded until the next day and this occurs during a winter's day, then the wet clay loaded onto the one or more transporting assets <NUM>, <NUM>, <NUM> may become solid rock. This will require additional efforts and incur further costs the following day for removing it from the one or more transporting assets <NUM>, <NUM>, <NUM> and lead to lost load-out capacity the next day for the site S of the mass excavation project. Alternatively, it may also result in that operators within the mass excavation project may avoid loading out transporting assets <NUM>, <NUM>, <NUM> at the end of a work shift, which then would lead to a reduced utilization of available transporting assets <NUM>, <NUM>, <NUM> and lower the efficiency of the mass excavation project. Hence, there is a need for improved management of mass excavation projects.

Examples of a method performed by a network system <NUM> for enabling management of a mass excavation project, wherein the mass excavation project is associated with one or more transporting assets <NUM>, <NUM>, <NUM> and one or more load destination sites T<NUM>, T<NUM>, will now be described with reference to the flowchart depicted in <FIG> is an illustrated example of actions, steps or operations which may be performed by the network system <NUM> described above with reference to <FIG>. Here, each load destination site T<NUM>, T<NUM> is associated with a maximum material weight receiving capacity. The method may comprise the following actions, steps or operations.

Action <NUM>. Initially, the network system <NUM> obtains, from a user device <NUM> associated with a transporting asset <NUM>, a first information indicating that the transporting asset <NUM> has been loaded with excavated material. This means, for example, that the network system <NUM> may be notified by the driver <NUM> of the transporting asset <NUM> that the transporting asset <NUM> has been loaded with excavated material at the site S of the mass excavation project and intends to transport the excavated material away from the site S of the mass excavation project.

Action <NUM>. After obtaining the first information in Action <NUM>, the network system <NUM> provides, to the user device <NUM> associated with the transporting asset <NUM>, a load receipt based on the obtained first information, whereby the load receipt is associated with a load destination site T<NUM> for depositing the excavated material. This means, for example, that the network system <NUM> may notify or confirm to the user device <NUM> of the transporting asset <NUM> that it has registered that the transporting asset <NUM> has been loaded with excavated material at the site S of the mass excavation project. Here, the network system <NUM> also dispatches, i.e. designates, and directs the driver <NUM> of the transporting asset <NUM> to one of the available destination sites T<NUM>, T<NUM> for depositing the excavated material. In other words, the network system <NUM> may select and associate the load receipt for the transporting asset <NUM> with a specific one of the available destination sites T<NUM>, T<NUM> for depositing the excavated material.

Action <NUM>. Subsequently, the network system <NUM> obtains, from the user device <NUM> associated with the transporting asset <NUM>, a second information indicating that the transporting asset <NUM> has off-loaded the excavated material at the load destination site T<NUM> and the weight of the excavated material. This means, for example, that the network system <NUM> is not only notified about the time when the transporting asset <NUM> off-loaded the excavated material at the load destination site T<NUM>, but also about the actual weight of the excavated material that was loaded onto the transporting asset <NUM> at the site S of the mass excavation project. This enable, for example, the network system <NUM> to set limitations that defines the total material weight receiving capacity of each of the load destination sites T<NUM>, T2 available to the mass excavation project, i.e. how much excavated material may be transported to each load destination sites T<NUM>, T2. This may apply to a single work shift or longer suitable defined periods of time for each particular load destination sites T<NUM>, T2.

Here, according to some examples, the obtained weight of the excavated material is a crowned or verified weight obtained at the load destination site by the user device associated with the transporting asset. A crowned or verified weight may here mean that a scale or weight measurement apparatus is used at the load destination site that has a certain approved or certified weight accuracy or tolerance level. This means that by using a crowned or verified weight, more accurate weight levels may be achieved. This may increase the accuracy of the continuous determination of the remaining material weight receiving capacity of each of the load destination sites T<NUM>, T2 available to the mass excavation project.

Action <NUM>. After obtaining the second set of information in Action <NUM>, the network system <NUM> determines a remaining material weight receiving capacity of the load destination site T<NUM> based on the obtained weight of the excavated material and the maximum material weight receiving capacity of the load destination site T<NUM>. This means, for example, that since the network system <NUM> may have access to, be configured with or comprise, information regarding the total material weight receiving capacity of each of the load destination sites T<NUM>, T2 available to the mass excavation project, the network system <NUM> may continuously update the remaining material weight receiving capacity of each of the load destination sites T<NUM>, T2 available to the mass excavation project. This advantageously allows the network system <NUM>, or user thereof, to apply corrective measures in order to avoid transporting assets <NUM>, <NUM>, <NUM> carrying excavated material from the site S of the mass excavation project to be dispatched to a load destination sites T<NUM>, T2 that is not capable of receiving the load of excavated material or closed. For example, as shown in <FIG>, instead of the transporting assets <NUM>, <NUM>, <NUM> carrying excavated material from the site S of the mass excavation project to a load destination site T<NUM> that is closed, e.g. due to receiving its maximum allowed material for the day, the transporting assets <NUM>, <NUM>, <NUM> may be dispatched to another load destination site, e.g. the load destination site T<NUM>. In other words, the network system <NUM> may select and associate the load receipt for the transporting asset <NUM> with a specific one of the available destination sites T<NUM>, T<NUM> for depositing the excavated material based on the remaining material weight receiving capacity of each of the load destination sites T<NUM>, T2 available to the mass excavation project.

Action <NUM>. Optionally, in some examples, the network system <NUM> may provide, to user devices associated with the one or more transporting assets <NUM>, <NUM>, <NUM> and/or user devices associated with the mass excavation project, information indicating the determined remaining material weight receiving capacity of the load destination site T<NUM>. This means, for example, that the network system <NUM> may notify the driver <NUM> of a transporting asset <NUM> carrying excavated material from the site S of the mass excavation project of which load destination site T<NUM>, T<NUM> is most advantageous to deposit the excavated material. Hence, the driver <NUM> of a transporting asset <NUM> may alter its route towards another load destination T<NUM>, T<NUM> if deemed necessary. According to another example, other personnel associated with the mass excavation project, such as, e.g. foremen, truck dispatchers, site managers, machine operators, etc., may use other user devices when provided with this information, e.g. wireless communication devices or other devices connected to the Internet. Thereby, a more efficient management of the mass excavation project is enabled.

Action <NUM>. According to some examples, the network system <NUM> may disable associations of load receipts to a load destination site T<NUM> when the remaining material weight receiving capacity of the load destination site T<NUM> falls below a predetermined threshold level. This means, for example, that the network system <NUM> may prevent a load destination site T<NUM>, T<NUM> that may be about to or have already exceeded its maximum capacity for the current work shift to be associated with a load receipt, i.e. no transporting assets <NUM>, <NUM>, <NUM> will no longer be dispatched to this particular load destination site T<NUM>, T<NUM>.

Action <NUM>. Additionally, in some examples, after obtaining the second set of information in Action <NUM>, the network system <NUM> may provide, to the user device <NUM> associated with the transporting asset <NUM>, a delivery receipt based on the obtained second information. This means, for example, that the network system <NUM> may notify or confirm to the user device <NUM> of the transporting asset <NUM> that it has registered that the transporting asset <NUM> has off-loaded the excavated material at the site S of the mass excavation project and the actual weight of the excavated material that was loaded onto the transporting asset <NUM> at the site S of the mass excavation project. Here, it should also be noted that a mass excavation project may include one or several different sites at which material is to be excavated and transported. The network system <NUM> may be arranged to handle one or more mass excavation projects and digitally associate each load and delivery receipt to a mass excavation project.

Examples of a method performed by a user device <NUM> associated with a transporting asset <NUM> for enabling management of a mass excavation project, will now be described with reference to the flowchart depicted in <FIG> is an illustrated example of actions, steps or operations which may be performed by the user device <NUM> described above with reference to <FIG>. The method may comprise the following actions, steps or operations.

Action <NUM>. Initially, the user device <NUM> provides, to a network system <NUM>, a first information indicating that the transporting asset <NUM> has been loaded with excavated material. This means, for example, that the user device <NUM> may be used by the driver <NUM> of the transporting asset <NUM> to notify the network system <NUM> that the transporting asset <NUM> has been loaded with excavated material at the site S of the mass excavation project and intends to transport the excavated material away from the site S of the mass excavation project.

Action <NUM>. In response to providing the first information to the network system <NUM> in Action <NUM>, the user device <NUM> obtains from the network system <NUM> a load receipt based on the provided first information, whereby the load receipt is associated with a load destination site T<NUM> for depositing the excavated material. This means, for example, that the user device <NUM> may receive a notification or confirmation that the network system <NUM> has registered that the transporting asset <NUM> has been loaded with excavated material at the site S of the mass excavation project. Here, the user device <NUM> also receives information from the network system <NUM> that directs the driver <NUM> of the transporting asset <NUM> to one of the available destination sites T<NUM>, T<NUM> for depositing the excavated material. In other words, the user device <NUM> may receive a load receipt that specifically indicate a specific one of the available destination sites T<NUM>, T<NUM> for the transporting asset <NUM> to deposit the excavated material.

Action <NUM>. Subsequently, the user device <NUM> receives, at the load destination site T<NUM> associated with the load receipt, information indicating the weight of the excavated material. This means, for example, that the user device <NUM> may, after receiving its load receipt in Action <NUM>, proceed with the transport of the excavated material towards the load destination site T<NUM> associated with the load receipt. As the transporting asset <NUM> arrives at the load destination site T<NUM>, the transporting asset <NUM> is normally weighed together with its loaded excavated material in order to determine the weight of the excavated material, i.e. load weight. The result of the weighing may be presented to the driver <NUM> of the transporting asset <NUM> which may input the result in the user device <NUM>. This may, for example, be performed by the driver <NUM> manually inputting the result in the user device <NUM> or automatically by scanning a barcode or OR-code indicating the result to the user device <NUM>. Here, according to some examples, the obtained weight of the excavated material may be a crowned or verified weight obtained at the load destination site T<NUM> by the user device <NUM> associated with the transporting asset <NUM>.

Action <NUM>. After receiving the information indicating the weight of the excavated material in Action <NUM>, the user device <NUM> provides, to the network system <NUM>, a second information indicating that the transporting asset <NUM> has off-loaded the excavated material at the load destination site T<NUM> and the received weight of the excavated material. This means, for example, that the user device <NUM> may notify the network system <NUM> regarding the time when the transporting asset <NUM> off-loaded the excavated material at the load destination site T<NUM>, and the actual weight of the excavated material that was loaded onto the transporting asset <NUM> at the site S of the mass excavation project. Thereby, a more efficient management of the mass excavation project is enabled.

Action <NUM>. Optionally, in some examples, the user device <NUM> trigger an alert in the user device <NUM> when the remaining material weight receiving capacity of a load destination site T<NUM> associated with an obtained the load receipt falls below a preconfigured threshold level. This means, for example, that the user device <NUM> may notify or indicate to the driver <NUM> of the transporting asset <NUM> carrying excavated material that its selected load destination site T<NUM> may, for example, be about to close or have already exceeded its maximum capacity for the current work shift. This means that the load destination site T<NUM> may not be available for the transporting asset <NUM> to make its deposit and that the transporting asset <NUM> should proceed to another destination site, e.g. the load destination site T<NUM>, for depositing its loaded excavated material.

To perform the method actions in a network system <NUM> for enabling management of a mass excavation project, wherein the mass excavation project is associated with one or more transporting assets <NUM>, <NUM>, <NUM> and one or more load destination sites T<NUM>, T<NUM>, wherein each load destination site T<NUM>, T<NUM> is associated with a maximum material weight receiving capacity, the network system <NUM> may comprise the following arrangement depicted in <FIG> shows a schematic block diagram of examples of a network system <NUM>. The examples of the network system <NUM> described herein may be considered as independent examples, or may be considered in any combination with each other to describe non-limiting examples. It should also be noted that, although not shown in <FIG>, it should be noted that known conventional features of a network system <NUM>, such as, for example, a connection to the mains, may be assumed to be comprised in the network system <NUM> but is not shown or described any further in regards to <FIG>.

The network system <NUM> may comprise one or more centrally located or distributed network unit(s), wherein the network system <NUM> and the one or more network unit(s) may comprise a processing circuitry <NUM> and a memory <NUM>. It should also be noted that some or all of the functionality described in the examples above as being performed by the first node <NUM> may be provided by the processing circuitry <NUM> executing instructions stored on a computer-readable medium, such as, the memory <NUM> shown in <FIG>. The processing circuitry <NUM> may also comprise an obtaining module <NUM>, a providing module <NUM>, a determining module <NUM>, and a disabling module <NUM>, each responsible for providing its functionality to support the examples described herein.

The network system <NUM> or processing circuitry <NUM> is configured to, or may comprise the obtaining module <NUM> configured to, obtain, from a user device <NUM> associated with a transporting asset <NUM>, a first information indicating that the transporting asset <NUM> has been loaded with excavated material. Also, the network system <NUM> or processing circuitry <NUM> is configured to, or may comprise the providing module <NUM> configured to, provide, to the user device <NUM> associated with the transporting asset <NUM>, a load receipt based on the obtained first information, whereby the load receipt is associated with a load destination site T<NUM> for depositing the excavated material. Further, the network system <NUM> or processing circuitry <NUM> is configured to, or may comprise the obtaining module <NUM> configured to, obtain, from the user device <NUM> associated with the transporting asset (<NUM>), a second information indicating that the transporting asset <NUM> has off-loaded the excavated material at the load destination site T<NUM> and the weight of the excavated material. Furthermore, the network system <NUM> or processing circuitry <NUM> is configured to, or may comprise the determining module <NUM> configured to, determine a remaining material weight receiving capacity of the load destination site T<NUM> based on the obtained weight of the excavated material and the maximum material weight receiving capacity of the load destination site T<NUM>.

In some examples, the network system <NUM> or processing circuitry <NUM> may be configured to, or may comprise the providing module <NUM> configured to, provide, to user devices associated with the one or more transporting assets <NUM>, <NUM>, <NUM> and/or user devices associated with the mass excavation project, information indicating the determined remaining material weight receiving capacity of the load destination site T<NUM>. In some examples, the network system <NUM> or processing circuitry <NUM> may be configured to, or may comprise the disabling module <NUM> configured to, disable associations of load receipts to a load destination site T<NUM> when the remaining material weight receiving capacity of the load destination site T<NUM> falls below a predetermined threshold level. According to some examples, the network system <NUM> or processing circuitry <NUM> may be configured to, or may comprise the providing module <NUM> configured to, provide, to the user device <NUM> associated with the transporting asset <NUM>, a delivery receipt based on the obtained second information. In some examples, the obtained weight of the excavated material is a crowned or verified weight obtained at the load destination site T<NUM> by the user device <NUM> associated with the transporting asset <NUM>.

Furthermore, the examples for enabling management of a mass excavation project described above may be implemented through one or more processors, such as the processing circuitry <NUM> in the network system <NUM> depicted in <FIG>, together with computer program code for performing the functions and actions of the examples herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code or code means for performing the examples herein when being loaded into the processing circuitry <NUM> in the network system <NUM>. The computer program code may e.g. be provided as pure program code in the network system <NUM> or on a server and downloaded to the network system <NUM>. Thus, it should be noted that the modules of the network system <NUM> may in some examples be implemented as computer programs stored in memory, e.g. in the memory modules <NUM> in <FIG>, for execution by processors or processing modules, e.g. the processing circuitry <NUM> of <FIG>. Those skilled in the art will also appreciate that the processing circuitry <NUM> and the memory <NUM> described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory, that when executed by the one or more processors such as the processing circuitry <NUM> perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

To perform the method actions in a user device <NUM> associated with a transporting asset <NUM> for enabling management of a mass excavation project, the user device <NUM> may comprise the following arrangement depicted in <FIG> shows a schematic block diagram of examples of a user device <NUM>. The examples of the user device <NUM> described herein may be considered as independent examples, or may be considered in any combination with each other to describe non-limiting examples. It should also be noted that, although not shown in <FIG>, it should be noted that known optional features of a user device <NUM>, such as, for example, at least one antenna and a power source, e.g. a battery or main connection, may be assumed to be comprised in the user device <NUM> in some examples, but is not shown or described any further in regards to <FIG>.

The user device <NUM> may comprise processing circuitry <NUM> and a memory <NUM>. It should also be noted that some or all of the functionality described in the examples above as being performed by the user device <NUM> may be provided by the processing circuitry <NUM> executing instructions stored on a computer-readable medium, such as, the memory <NUM> shown in <FIG>. The processing circuitry <NUM> may also comprise Alternative examples of the user device <NUM> may comprise a providing module <NUM>, a obtaining module <NUM>, an receiving module <NUM>, and a triggering module <NUM>,, each responsible for providing its functionality to support the examples described herein.

The user device <NUM> or processing circuitry <NUM> is configured to, or may comprise the providing module <NUM> configured to, provide, to a network system <NUM>, a first information indicating that the transporting asset <NUM> has been loaded with excavated material. Also, the user device <NUM> or processing circuitry <NUM> is configured to, or may comprise the obtaining module <NUM> configured to, obtain, from the network system <NUM>, a load receipt based on the provided first information, whereby the load receipt is associated with a load destination site T<NUM> for depositing the excavated material. Further, the user device <NUM> or processing circuitry <NUM> is configured to, or may comprise the receiving module <NUM> configured to, receive at the load destination site T<NUM> associated with the load receipt, information indicating the weight of the excavated material. Furthermore, the user device <NUM> or processing circuitry <NUM> is configured to, or may comprise the providing module <NUM> configured to, provide, to the network system <NUM>, a second information indicating that the transporting asset <NUM> has off-loaded the excavated material at the load destination site T<NUM> and the received weight of the excavated material.

In some examples, the user device <NUM> or processing circuitry <NUM> may be configured to, or may comprise the triggering module <NUM> configured to, trigger an alert in the user device <NUM> when the remaining material weight receiving capacity of a load destination site T<NUM> associated with an obtained the load receipt falls below a preconfigured threshold level.

Furthermore, the examples for enabling management of a mass excavation project described above may be implemented through one or more processors, such as the processing circuitry <NUM> in the user device <NUM> depicted in <FIG>, together with computer program code for performing the functions and actions of the examples herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code or code means for performing the examples herein when being loaded into the processing circuitry <NUM> in the user device <NUM>. The computer program code may e.g. be provided as pure program code in the user device <NUM> or on a server and downloaded to the user device <NUM>. Thus, it should be noted that the modules of the user device <NUM> may in some examples be implemented as computer programs stored in memory, e.g. in the memory modules <NUM> in <FIG>, for execution by processors or processing modules, e.g. the processing circuitry <NUM> of <FIG>. Those skilled in the art will also appreciate that the processing circuitry <NUM> and the memory <NUM> described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory, that when executed by the one or more processors such as the processing circuitry <NUM> perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

<FIG> is a schematic diagram of a computer system <NUM> for implementing examples disclosed herein. The computer system <NUM> is adapted to execute instructions from a computer-readable medium to perform these and/or any of the functions or processing described herein. The computer system <NUM> may be connected (e.g., networked) to other machines in a LAN, an intranet, an extranet, or the Internet. While only a single device is illustrated, the computer system <NUM> may include any collection of devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. Accordingly, any reference in the disclosure and/or claims to a computer system, computing system, computer device, computing device, control system, control unit, electronic control unit (ECU), processor device, etc., includes reference to one or more such devices to individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. For example, control system may include a single control unit or a plurality of control units connected or otherwise communicatively coupled to each other, such that any performed function may be distributed between the control units as desired. Further, such devices may communicate with each other or other devices by various system architectures, such as directly or via a Controller Area Network (CAN) bus, etc..

The computer system <NUM> may comprise at least one computing device or electronic device capable of including firmware, hardware, and/or executing software instructions to implement the functionality described herein. The computer system <NUM> may include a processor device <NUM> (may also be referred to as a control unit), a memory <NUM>, and a system bus <NUM>. The computer system <NUM> may include at least one computing device having the processor device <NUM>. The system bus <NUM> provides an interface for system components including, but not limited to, the memory <NUM> and the processor device <NUM>. The processor device <NUM> may include any number of hardware components for conducting data or signal processing or for executing computer code stored in memory <NUM>. The processor device <NUM> (e.g., control unit) may, for example, include a general-purpose processor, an application specific processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a circuit containing processing components, a group of distributed processing components, a group of distributed computers configured for processing, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The processor device may further include computer executable code that controls operation of the programmable device.

The system bus <NUM> may be any of several types of bus structures that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and/or a local bus using any of a variety of bus architectures. The memory <NUM> may be one or more devices for storing data and/or computer code for completing or facilitating methods described herein. The memory <NUM> may include database components, object code components, script components, or other types of information structure for supporting the various activities herein. Any distributed or local memory device may be utilized with the systems and methods of this description. The memory <NUM> may be communicably connected to the processor device <NUM> (e.g., via a circuit or any other wired, wireless, or network connection) and may include computer code for executing one or more processes described herein. The memory <NUM> may include non-volatile memory <NUM> (e.g., read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.), and volatile memory <NUM> (e.g., random-access memory (RAM)), or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a computer or other machine with a processor device <NUM>. A basic input/output system (BIOS) <NUM> may be stored in the non-volatile memory <NUM> and can include the basic routines that help to transfer information between elements within the computer system <NUM>.

A number of modules can be implemented as software and/or hard-coded in circuitry to implement the functionality described herein in whole or in part. The modules may be stored in the storage device <NUM> and/or in the volatile memory <NUM>, which may include an operating system <NUM> and/or one or more program modules <NUM>. All or a portion of the examples disclosed herein may be implemented as a computer program product <NUM> stored on a transitory or non-transitory computer-usable or computer-readable storage medium (e.g., single medium or multiple media), such as the storage device <NUM>, which includes complex programming instructions (e.g., complex computer-readable program code) to cause the processor device <NUM> to carry out the steps described herein. Thus, the computer-readable program code can comprise software instructions for implementing the functionality of the examples described herein when executed by the processor device <NUM>. The processor device <NUM> may serve as a controller or control system for the computer system <NUM> that is to implement the functionality described herein.

The computer system <NUM> also may include an input device interface <NUM> (e.g., input device interface and/or output device interface). The input device interface <NUM> may be configured to receive input and selections to be communicated to the computer system <NUM> when executing instructions, such as from a keyboard, mouse, touch-sensitive surface, etc. Such input devices may be connected to the processor device <NUM> through the input device interface <NUM> coupled to the system bus <NUM> but can be connected through other interfaces such as a parallel port, an Institute of Electrical and Electronic Engineers (IEEE) <NUM> serial port, a Universal Serial Bus (USB) port, an IR interface, and the like. The computer system <NUM> may include an output device interface <NUM> configured to forward output, such as to a display, a video display unit (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system <NUM> may also include a communications interface <NUM> suitable for communicating with a network as appropriate or desired.

According to some additional examples, a control system comprising one or more control units configured to perform the method according to any of the examples described above is also provided.

Claim 1:
A method performed by a network system (<NUM>) for enabling management of a mass excavation project, wherein the mass excavation project is associated with one or more transporting assets (<NUM>, <NUM>, <NUM>) and one or more load destination sites (T<NUM>, T<NUM>), wherein each load destination site (T<NUM>, T<NUM>) is associated with a maximum material weight receiving capacity, the method comprising:
obtaining (<NUM>), from a user device (<NUM>) associated with a transporting asset (<NUM>), a first information indicating that the transporting asset (<NUM>) has been loaded with excavated material;
providing (<NUM>), to the user device (<NUM>) associated with the transporting asset (<NUM>), a load receipt based on the obtained first information, whereby the load receipt is associated with a load destination site (T<NUM>) for depositing the excavated material;
obtaining (<NUM>), from the user device (<NUM>) associated with the transporting asset (<NUM>), a second information indicating that the transporting asset (<NUM>) has off-loaded the excavated material at the load destination site (T<NUM>) ;
wherein the method is characterized in that the second information indicates the weight of the excavated material and by comprising:
determining (<NUM>) a remaining material weight receiving capacity of the load destination site (T<NUM>) based on the obtained weight of the excavated material and the maximum material weight receiving capacity of the load destination site (T<NUM>).