The present invention relates to the management of physical assets and in particular, but not limited to, the management of physical assets comprising plant equipment such as materials handling vehicles/machinery, construction vehicles/machinery, and the like. One of the main environmental challenges facing large scale suppliers and large scale users of equipment, such as heavy duty plant equipment, at several different geographic locations is the environmental impact of transporting the equipment from the supplier's base to the location at which it is required. This problem can be compounded both by supplier and end user behaviour. For example, large scale users may seek to manage financial costs by use of short term equipment hire contracts (e.g. a few days to a few months) to ensure that equipment hire time is minimised thereby resulting in a relatively lean operation in which the amount of equipment being leased at any one time is minimised. This, in turn, can lead to a disproportionately large number of 'transport to client' and 'return to base' journeys and an associated disproportionately large environmental impact. In the case of the equipment supplier, consolidation of equipment into a single (or relatively few) equipment hubs (e.g. to realise reduced real estate costs) can result in a relatively large average distances between the supplier's hub and the locations at which the equipment is required by the equipment user.

Other challenges also face large scale suppliers and large scale users of equipment. One such challenge, relates to the large differences in usage patterns of the different assets provided to a user for use at different locations. These different usage patterns can lead to large differences in the level of wear and tear experienced by the different assets and can result in an increased frequency of service calls to overused assets whilst other assets remain underutilised. There is, therefore, a need for improved asset management and asset provisioning methods.

Supply / transfer based on presence in virtual pool

Accordingly one aspect of the present invention provides a computer implemented method of managing provision of physical assets to an asset user, the method comprising: initiating physical provision of a plurality of assets to an asset user for use at a plurality of different geographic locations; maintaining an inventory of provided assets for said asset user in association with data identifying a location of each provided asset, data identifying at least one capability of each provided asset, and data indicating the availability of each provided asset; grouping a subset of provided assets from said inventory in a virtual pool of available assets based on said availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location; providing an interface for use by the asset user to manage said plurality of assets; receiving a request from an asset user, via said interface, for an asset having a required capability at a specified location; and responding to said request in dependence on the availability of an asset having said required capability in said virtual pool wherein said responding step comprises: initiating physical transfer of an available asset from its respective location to the specified location when an asset having said required capability is available in said virtual pool; and initiating physical supply of a further asset, in addition to the provided assets in the current inventory, when an asset having said required capability is not available in said virtual pool. Another aspect provides a computer implemented method of managing physical assets provided to an asset user by an asset provider wherein said provided assets are distributed between different sites at different geographic locations, the method comprising: generating an interface for use by the asset user to manage said plurality of assets, the interface providing: access to an inventory of provided assets for said asset user in association with data identifying a location of each provided asset, data identifying at least one capability of each provided asset, and data indicating the availability of each provided asset; access to a grouping comprising a subset of provided assets from said inventory in a virtual pool of available assets based on said availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location; means for generating a request for transfer of an available asset having the required capability from its respective location to a specified location, when said asset having the required capability is available in said virtual pool; and means for generating a request for supply of a further asset in addition to the current inventory and having the required capability to a specified location, when said asset having the required capability is not available in said virtual pool.

Unlike existing asset management systems in which the hire (or purchase) of new assets is divorced from the management of existing assets, therefore, this aspect (and other aspects described below) provides a more integrated system. The asset provider and the asset user can thus manage provision of physical assets in a carbon efficient manner in which the assets provided to a user can be moved directly from a site at which they are not currently required to a site at which they are required without unnecessary 'return to base' and 'transport to client' journeys.

The integrated system also has other benefits both for the provider and the asset user. The providers of the physical assets are, for example, able to reduce the number of equipment supply hubs further and/or reduce the number of physical assets kept at the hub(s) as a reserve against possible supply requests from asset users thereby allowing the providers to reduce the real estate required to store the vehicles. The asset users are provided with an effective asset management tool which allows them to use the assets which they have hired in a more effective and efficient manner, for example, by moving an asset from a location at which it is no longer required to a nearby location at which it is required rather than returning the available asset to the asset provider's hub whilst simultaneously ordering another asset having the same or a similar capability.

When an asset having said required capability is available in said virtual pool, the initiation of transfer of an available asset from its respective location to the specified location may, nevertheless, be subject to an analysis of data indicating an impact associated with the transfer of the available asset to the specified location (or associated with use of each available asset) and data indicating a corresponding impact associated with the supply of a further asset (or associated with use of each available asset). For example, if supply (or use) of a further asset will have a lower impact than transfer (or use) of the available asset having the required capability then the supply of a further asset may be initiated in preference to transfer of the available asset.

Thus, when it is less carbon (and/or cost) efficient to move an available asset than supply a fresh asset, a fresh asset may be supplied in preference to moving a previously supplied asset. Similarly, if an asset can be supplied which is better suited to the specified location than the previously supplied asset (e.g. due to terrain type, height, width or weight constraints, or the like), and/or which is better suited to the task it is to be used for, then an additional asset may be supplied in preference to moving a previously supplied asset. When a plurality of assets having said required capability are available in the virtual pool, an asset may be selected for transfer in dependence on the data indicating an impact associated with the transfer of each available asset to the specified location (or associated with use of each available asset).

The interface for use by the asset user to manage said plurality of assets, may provide: means for said asset user to request, using said interface, transfer of a provided asset from its respective location to another specified location; and/or means for said asset user to request, using said interface, supply of a further asset in addition to the current inventory. Thus, the received request may comprise an explicit or an implicit transfer request and/or may comprise an explicit or an implicit supply request. The received request may comprise a general request for an asset having a required capability at a specified location.

The assets provided by the asset provider may be provided from assets owned by the provider or from assets sourced by the provider from the owner of the asset, or purchased. Asset user controlled supply / transfer request

Another aspect provides a computer implemented method of managing provision of physical assets to an asset user, the method comprising: initiating physical provision of a plurality of assets to an asset user for use at a plurality of different geographic locations; maintaining an inventory of provided assets for said asset user; providing an interface for use by the asset user to manage said plurality of assets, the interface providing: means for generating a request for transfer of a provided asset from its respective location to another specified location; and means for generating a request for supply of a further asset in addition to the current inventory; receiving a request generated using said interface, for an asset having a required capability at a specified location; and responding to said request by: initiating physical transfer of a provided asset from its respective location to the specified location when the request is a transfer request; or initiating physical supply of a further asset, in addition to the provided assets in the current inventory, when the request is a supply request.

Another aspect provides a computer implemented method of managing physical assets provided to an asset user by an asset provider wherein said provided assets are distributed between different sites at different geographic locations, the method comprising: generating an interface for use by the asset user to manage said plurality of assets, the interface providing: access to an inventory of provided assets for said asset user; means for generating a request for transfer of a provided asset from its respective location to another specified location; and means for generating a request for supply of a further asset in addition to the current inventory. In this manner, the asset user is provided with an integrated tool for managing their inventory by generating a specific (explicit or implicit) transfer or supply request in dependence on the needs of the asset user, thereby allowing the asset user greater control over the supply of assets and accordingly greater flexibility to manage the supply of assets to them in an efficient manner which minimises the environmental impact of the supply.

The inventory of provided assets for said asset user may comprise details of each provided asset in association with data identifying a location of each provided asset, may comprise data identifying at least one capability of each provided asset, and/or may comprise data indicating the availability of each provided asset. The inventory may include a group comprising a subset of provided assets from said inventory in a virtual pool of available assets based on availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location.

The interface may comprise means for providing details of the assets available in said virtual pool to said asset user, via said interface, to allow said asset user to determine if an asset having a required capability is available in said virtual pool. A transfer request may be generated when said asset having the required capability is available in said virtual pool. A supply request may be generated when said asset having the required capability is not available in said virtual pool.

The interface may provide means to remove an available asset from the virtual pool. Asset user interface

Another aspect of the present invention provides a interface for managing physical assets provided to an asset user by an asset provider wherein said provided assets are distributed between different geographic locations, the interface providing: access to an inventory of provided assets for said asset user in association with data identifying a location of each provided asset, data identifying at least one capability of each provided asset, and data indicating the availability of each provided asset; access to a grouping comprising a subset of provided assets from said inventory in a virtual pool of available assets based on said availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location; means for generating a request for transfer of an available asset having the required capability from its respective location to a specified location, when said asset having the required capability is available in said virtual pool; and means for generating a request for supply of a further asset in addition to the current inventory and having the required capability to a specified location, when said asset having the required capability is not available in said virtual pool.

Transfer between a plurality of different asset users

Another aspect of the present invention provides a computer implemented method of managing provision of physical assets to a plurality of asset users, the method comprising: initiating physical provision of a plurality of assets to each asset user for use at a plurality of different geographic locations; maintaining an inventory of provided assets for each asset user in association with data identifying a location of each provided asset, data identifying at least one capability of each provided asset, and data indicating the availability of each provided asset; grouping, for each asset user, a subset of provided assets from said inventory in a virtual pool of available assets for that asset user, based on said availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location by the asset user for which it was provided; providing an interface for use by each asset user to manage the respective plurality of assets provided to that asset user; receiving a request from an asset user, via said interface, for an asset having a required capability at a specified location; and responding to said request in dependence on the availability of an asset having said required capability in at least one of said virtual pools, wherein said responding step comprises: managing transfer of an available asset from its respective location to the specified location, when an asset having said required capability is available in at least one of said virtual pools; and initiating physical supply of a further asset, in addition to the provided assets in the current inventory of the asset user making the request, when an asset having said required capability is not available in at least one of said virtual pools. The plurality of asset users may be asset users belonging to different organisations or to a single organisation. For example, an asset user may comprise a manager of a subset (e.g. a division manager) of all the provided assets (e.g. a fleet) of a particular organisation (e.g. a fleet operator) or a manager of all the provided assets of the organisation (e.g. a fleet controller). When an asset having said required capability is available in the virtual pool of said asset user making the request the transfer may comprise transfer of an available asset from the virtual pool of the asset user making the request.

The transfer may comprise transfer of an available asset from the virtual pool of a further asset user when an asset having said required capability is available in the virtual pool of said further asset user.

When a plurality of assets having said required capability are available in one or more of the plurality of virtual pools, an asset may be selected for transfer in dependence on data indicating an impact associated with the transfer of each available asset to the specified location (or associated with use of each available asset). For example, a transfer having the lowest (or a lower) impact may be selected in preference to a transfer having a highest (or a higher) impact. The impact may comprise: a carbon cost; an estimated efficiency of using the equipment; and/or some other environmental impact or cost assessment. The data indicating the impact may, for example, comprise: data representing the respective distance between each location of an available asset and the specified location; data representing the respective fuel required to transport each available asset to the specified location; data representing the respective weight of each available asset having the required capability; data representing an estimated fuel efficiency of each available asset; data representing a respective environmental, financial, and or physical cost associated with transporting each available asset to the specified location and/or using each available asset; data representing a respective transport requirement for fulfilling the request by transfer of each available asset to the specified location; and/or the like.

When an asset having the required capability is available in the virtual pool of the asset user making the request, and an asset having said required capability is available in the virtual pool of a further asset user, transfer of an available asset from the virtual pool of the asset user making the request may be initiated in preference to transfer of an available asset from the virtual pool of the further asset user. The asset for transfer may, nevertheless, be selected for transfer in dependence on data indicating an impact associated with the transfer of each available asset to the specified location (or associated with use of each available asset).

Supply I transfer from virtual pool based on transport requirement

Another aspect of the present invention provides a computer implemented method of managing provision of physical assets to an asset user, the method comprising: initiating physical provision of a plurality of assets to an asset user for use at a plurality of different geographic locations; maintaining an inventory of provided assets for said asset user in association with data identifying a location of each provided asset and data indicating the availability of each provided asset (and optionally data identifying at least one capability of each provided asset); grouping a subset of provided assets from said inventory in a virtual pool of available assets based on said availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location; providing an interface for use by the asset user to manage said plurality of assets; receiving a request from at least one asset user, via said interface, for an asset at a specified location; and responding to said request in dependence on the availability of an asset in said virtual pool wherein said responding step comprises: comparing data indicating an impact of fulfilling said request from said virtual pool with data indicating an impact of fulfilling said request by supply of a further asset, when an asset having said required capability is available in said virtual pool, and initiating fulfilment of said request from said virtual pool, or by supply of a further asset, in dependence on a result of said comparison .

Another aspect of the present invention provides a computer implemented method of managing provision of physical assets to an asset user, the method comprising: initiating physical provision of a plurality of assets to an asset user for use at a plurality of different geographic locations; maintaining an inventory of provided assets for said asset user in association with data identifying a location of each provided asset and data indicating the availability of each provided asset (and optionally data identifying at least one capability of each provided asset); grouping a subset of provided assets from said inventory in a virtual pool of available assets based on said availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location; providing an interface for use by the asset user to manage said plurality of assets; receiving a request from at least one asset user, via said interface, for an asset at a specified location; responding to said request, when there are a plurality of available assets in said virtual pool, by comparing respective data indicating an impact of transporting each said available asset to said specified location; selecting an available asset to fulfil said request from said virtual pool in dependence on a result of said comparison; and initiating physical transport of the selected asset to said specified location. Thus, when there is a choice of ways in which a particular request for an asset can be fulfilled, the most efficient way (e.g. the way having the lowest impact) may be initiated thereby helping to minimise the environmental impact and/or financial cost of providing the asset at the specified location. For example a decision to supply a fresh asset or to transfer of an existing asset may be based on geographical proximity of the specified location to the hub from which the fresh asset will be supplied and to the physical locations of any suitable assets in the virtual pool.

Reduction in service calls by managed usage

Another aspect provides a computer implemented method of managing provision of physical assets to an asset user, the method comprising: initiating physical provision of a plurality of assets to an asset user for use at a plurality of different geographic locations; maintaining an inventory of provided assets for said asset user in association with data identifying a location of each provided asset, (optionally data identifying at least one capability of each provided asset) and data indicating usage of each provided asset; obtaining an indication that an exchange of a first provided asset having a first usage level with a second provided asset having a second usage level is required; wherein the second usage level is lower than the first usage level; and managing said exchange of the first provided asset with said second provided asset.

The method may comprise assessing the data indicating the respective usage of each provided asset and obtaining said indication that an exchange is required based on said assessment. The method may comprise providing an interface for use by the asset user to manage said plurality of assets and obtaining said indication, via said interface, that said exchange is required.

Another aspect provides a computer implemented method of managing physical assets provided to an asset user by an asset provider wherein said provided assets are distributed between different sites at different geographic locations, the method comprising: generating an interface for use by the asset user to manage said plurality of assets, the interface providing: access to an inventory of provided assets for said asset user in association with data identifying a location of each provided asset, data identifying at least one capability of each provided asset, and data indicating the usage of each provided asset; means for assessing the data indicating the respective usage of each provided asset; and means for initiating an exchange of a first provided asset having a first usage level with a second provided asset having a second usage level lower than the first usage level (and a similar capability to a capability of the first provided asset), in dependence on the usage assessment for the first and the second provided asset respectively. Thus, future usage of the first provided asset may be reduced and future usage of the second provided asset may be increased. In this manner, the usage of a plurality of assets having similar capabilities can be managed more effectively by swapping assets which are used less frequently or less intensively with assets which are used more frequently or more intensively thereby effectively "averaging out" usage over a plurality of physical assets. Thus, when a routine usage based service calls is scheduled, a service engineer may visit the locations of a plurality of similarly used assets provided for a particular asset user on a single service occasion without the need to return to base in between. This helps to reduce the frequency of service calls thereby reducing their environmental and financial impact. Moreover, this can reduce the frequency with which physical assets that have reached or exceeded their contracted usage need to be returned to base. It also can reduce the excess usage charges levied on an asset user for exceeding a contracted usage limit for a particular overused asset whilst other assets having a similar capability are underused.

Management based on service history

The inventory may further comprise data representing a service history of each provided asset. The assessing means may be configured for assessing the data representing the service histories of each provided asset. The exchange initiating and/or managing means may be configured for initiating/managing an exchange, in dependence on said assessment of the data representing the service histories, of a provided asset having a relatively poor service history (e.g. a history indicating an above average or above threshold number of routine and/or non-routine service calls) with a provided asset having a better service history than, a lower usage level than, and a similar capability to, the asset having the relatively poor service history. The service history may be assessed by reference to data indicating the seriousness of a fault discovered during a service call. The exchange initiating and/or managing means may be configured for initiating/managing an exchange, in dependence on said assessment of the data representing the service histories, of a provided asset having a relatively poor service history with a further asset in addition to the provided assets represented in the current inventory.

Review based on presence in virtual pool Another aspect provides a computer implemented method of managing physical assets provided to an asset user by an asset provider wherein said provided assets are distributed between different sites at different geographic locations, the method comprising: generating an interface for use by the asset user to manage said plurality of assets, the interface providing: access to an inventory of provided assets for said asset user in association with data identifying a location of each provided asset, and data indicating the availability of each provided asset; access to a grouping comprising a subset of provided assets from said inventory in a virtual pool of available assets based on said availability data, wherein each available asset in said virtual pool comprises an asset that is not currently required for use at its respective location; means for generating a request for supply of a further asset in addition to the current inventory to a specified location; means for reviewing said request for supply of a further asset in addition to the current inventory and for approving or rejecting said request in dependence on the whether said request for supply of a further asset can be fulfilled by transfer of an available asset in said virtual pool, whereby said request for supply of a further asset is rejected if said request for supply of a further asset can be fulfilled by transfer of an available asset in said virtual pool.

Thus, in addition to the environmental advantages, reviewing of supply requests based on the availability of a suitable asset in the virtual pool prior to submission of the request to an asset provider, advantageously reduces the submission of unnecessary requests. This provides benefits in terms of reduced network traffic, reduced workload for the asset provider management entity, and avoids the system becoming clogged with inappropriate requests.

A preferable embodiment of the invention also provides a computer program and a computer program product for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein, and a computer readable medium having stored thereon a program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein.

A preferable embodiment of the invention also provides a signal embodying a computer program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein, a computer implemented method of transmitting such a signal, and a computer product having an operating system which supports a computer program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein. A preferable embodiment of the invention extends to methods and/or apparatus substantially as herein described with reference to the accompanying drawings.

Any feature in one aspect of the invention may be applied to other aspects of the invention, in any appropriate combination. In particular, method aspects may be applied to apparatus aspects, and vice versa. Furthermore, features implemented in hardware may generally be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly.

According to the present invention, there is provided a radar system as set out in the corresponding independent claims. Other preferable features of the invention are recited in the dependent claims. Embodiments of the invention will now be described, by way of example only, with reference to the attached figures in which:

Figure 1 is a simplified illustration of the geographic coverage and distribution of a fleet operator's work sites; Figure 2 is a simplified illustration of a 'transfer ¹ based asset management model;

Figure 3 is a simplified schematic of an asset management tool for managing assets in accordance with the asset management model of Figure 2;

Figure 4 is a simplified overview of an asset management interface;

Figure 5 is a simplified flow chart illustrating generation and processing of a fluctuation asset management request;

Figure 6 is a simplified flow chart illustrating generation and processing of a transfer asset management request;

Figure 7 is a simplified flow chart illustrating generation and processing of a short term hire asset management request; Figure 8 is a simplified flow chart illustrating generation and processing of a division details modification management request; and

Figure 9 is a simplified illustration of an implementation of the asset management tool as part of a computer network.

Overview Figure 1 shows the geographic coverage and distribution of a particular asset user's work sites/locations. The asset user, in the illustrated example, comprises an fleet operator 10 (a fleet asset user) having a multitude of sites 12 at many different locations spread throughout a particular geographic region 14 each having different and varying requirements for physical assets 16 for use at the work sites 12. In this embodiment, the physical assets 16 comprise plant assets including vehicular assets, other equipment/machinery assets and attachment assets for the vehicular/equipment/machinery assets. In particular, the physical assets comprise materials handling assets such as materials handling vehicles/equipment including forklift trucks, warehouse equipment, trailers, tow tractors, container handlers, agricultural tractors and the like, and related attachments.

The physical assets are provided by an asset provider 18 (fleet provider) who maintains an inventory of the different assets provided to the fleet operator. The fleet operator's sites 12, and the physical assets used at those sites, are each assigned to a respective fleet division 20 such that each division comprises at least one work site/location 10 or possibly a plurality of work sites. Each division 20 is assigned to at least one fleet division manager (and associated deputy/alternate) for the management of assets 16 used within that division 20. Overall management of the fleet operator's entire fleet of assets 16 is assigned to at least one fleet controller, who is responsible for managing requests from fleet managers for the addition, transfer and/or removal of assets from the sites at which they are located.

There may be a plurality of fleet controllers that are responsible for managing the requests generated by division managers or other users. In this case the fleet controllers may be grouped into one or more groups (e.g. a central management team / fleet control group) referred to collectively as 'fleet control'. In this embodiment the membership of the central management team / fleet control group are administered by the asset provider as a service to the organisation to which the assets are provided. In this embodiment, the asset provider 18 provides an asset management tool for use by the fleet operator 10 to manage and keep track of the assets 16 provided to the fleet operator's fleet. The management tool allows the fleet operator to manage their fleet based on a 'transfer' based asset management model as illustrated in Figure 2.

In accordance with the 'transfer' based asset management model, the asset management tool allows the division managers (or fleet control) to place assets which are no longer required, which are currently not being used, or which are only rarely used (e.g. under-utilised) into a virtual pool 40 of available assets which virtual pool represents a sub-set of the provided assets in the inventory maintained by the asset provider.

The asset management tool allows the division managers or fleet controller to request provision or return of physical assets 42 and allows the division managers or fleet controller to request transfer 44 of an available asset in the virtual pool 40. In operation, requests for provision/return/transfer of assets are subject to an approval procedure in which requests submitted by division managers to fleet control for an initial review, are then passed on to the asset provider to determine the requirements for facilitating the transfer, are reviewed further by fleet control in dependence on the requirements for facilitating the transfer, and are approved or rejected based on the fleet control review. If the requests are approved, the asset provider 18 actions the approved request by managing the requested provision, reduction and/or transfer.

In this manner, the usage of a plurality of assets having similar capabilities can be managed more effectively by swapping assets which are used less frequently or less intensively with assets which are used more frequently or more intensively thereby effectively "averaging out" usage over a plurality of physical assets. Thus, when a routine usage based service calls is scheduled, a service engineer may visit the locations of a plurality of similarly used assets provided for a particular asset user on a single service occasion without the need to return to base in between. This helps to reduce the frequency of service calls thereby reducing their environmental and financial impact. Moreover, this can reduce the frequency with which physical assets that have reached or exceeded their contracted usage need to be returned to base. It also can reduce the excess usage charges levied on an asset user for exceeding a contracted usage limit for a particular overused asset whilst other assets having a similar capability are underused.

Asset Management Tool

Figure 3 is a simplified schematic of an asset management tool for managing assets in accordance with the 'transfer' based asset management model.

The asset management tool comprises an interface 68, which is accessible by authorised users of the fleet operator 10 and authorised users of the asset provider 18 including, for example, fleet controllers 60, division managers 62, and the like.

The interface 68 is implemented as a computer based interface that is accessible over a computer network such as the internet and comprises a plurality of functional modules including a fleet division management module 64, a fleet controller management module 66, and an asset provision management module 70. The interface 68, for example, may be implemented as a web portal or the like.

The fleet division management module 64 handles interaction with the fleet managers and the related processing including the generation of several different requests including fluctuation (asset increase/decrease requests), transfer requests, service calls, short term hire requests, requests for changes of division details and the addition or removal of a divisions assets from the virtual pool 40. Where division related processes are automated the fleet division management module 64 handles this automation. The fleet controller management module 66 handles interaction with the fleet control and the related processing including: the processing, review and approval/rejection of requests from division managers; managing the fulfilment of request where this can be done internally within the fleet operator" operation. Where control related processes such as reviewing and approving requests are automated, the fleet control management module 66 handles this automation.

The asset provision management module 70 handles interaction with the asset provide and the related processing including: processing, review and approval/rejection of requests approved by fleet control; managing the fulfilment of requests; managing the arrangement of site visits (e.g. for service calls, training, and/or application/requirement surveys). Where asset provision related processes such as managing the fulfilment of requests are automated, the asset provision management module 70 handles this automation. The asset management tool maintains an inventory 74 of the provided assets on behalf of the fleet operator 10 and administers the virtual pool 40 within this inventory 74. The inventory 74 forms part of the asset providers own inventory 72 of the assets that they either own or have hired from another party. The asset management tool also maintains an associated database 80 which includes the information 80 relating to the provided assets which is required to administer the asset management tool including, for example, technical and other information for each provided asset, address and contact information for each division and the associated site locations or sub-locations, service history information, and other information described throughout the description etc. As illustrated in Figure 9, the asset management tool may be implemented on a computer network 100. The computer network comprises an asset provider computer 110 and division manager computer 120, 120'. The asset provider computer is associated with a processor 112 coupled to a memory 170 for storing database 78. In the example of Figure 9, database 78 comprises a plurality of records 172 each record indicating an asset identifier and at least one asset attribute. Asset provider computer 110 is coupled via network 100 to division manager computers 120, 120'. Fleet control computer 130 is coupled via network 100 to asset user computers 120, 120' and to the asset provider computer 110. Transport provider entity 140 is coupled via network 100 to fleet control computer 130, to division manager computers 120, 120', and to the asset provider computer 110.

In operation, to provide a virtual pool of assets a processor 112 associated with asset provider computer 110 stores a plurality of records in memory each record identifying an asset and an asset location. Division manager computer 120 transmits an asset requirement in the form of a request such as a fluctuation request, an equipment movement request, short term hire request or a change division details request via network 100 to fleet control computer 130. Fleet control computer 130 evaluates the request and determines whether to transmit the request to asset provider computer 110. If it is determined that the request should be transmitted asset provider computer 110 receives the request and processor 112 generates a query of database 78 based on the request. In response to this query, database 178 returns one or more records 172 to processor 112.

Database 78 and memory 170 store a list which provides an inventory of provided assets for each division manager 120, 120' associated with a location (and optionally a location of each asset, if different from the division manager), data identifying asset capability such as load bearing capacity or lift reach and availability of each provided asset. Processor 112 stores in memory 170 a list of a subset 174 of assets based on their availability and provides an indication of this availability and location information in the form of asset management interface 114 which is stored in memory 170 and updated based on the subset list/availability information for provision to division manager and fleet management computers via network 100.

The asset management tool and its operation will now be described in more detail with reference to Figures 4 to 8. Registration Interface

In order to use the asset management tool to access data and reports a division manager (or other user) is required to register. Accordingly, the management tool is provided with a registration interface via which a division manager (or other user) may register by entering registration information including, for example, identification information, contact information, and details of the fleet division or divisions for which the division manager is responsible. The details provided are verified by the fleet management entity and, upon successful verification, a user identifier and password are generated and sent to the division manager (or other user) using the contact details provided (e.g. as an email to a specified email address). Log on interface

Once registered, a division manager (or other user) is able to log on by first accessing a log on interface provided by the management tool (e.g. by clicking a "LOGIN" indicium) or by attempting to access a reporting section of the management tool (e.g. by clicking a "REPORTS" indicium) both of which initiate appearance of the log on interface. The log on interface comprises input regions via which the user name and password can be entered. On successful entry of the information, the interface provides access to a reporting interface.

Reporting Interface

The reporting interface provides access to an inventory of the assets provided to the fleet operator. The available access includes access to a plurality of different reports providing:

Asset Details - e.g. details of each provided assets specification, capabilities, and any associated usage data;

Age Profile - e.g. details of the age profile of the provided assets; Service History - e.g. details of each provided asset's service history;

Allocation list by division - e.g. details of the provided assets allocated to a particular fleet division;

Availability Summary - e.g. a summary of the provided assets' availability; Late UDR - e.g. information on provided assets for which usage data has not been entered;

Forms Dashboard - e.g. details of the progress of transactions involving the provided assets; and

Virtual Equipment Pool - details of the provided assets that are available in the virtual pool for transfer to another location within the current division or in a different division.

The available access includes access to a plurality of different interfaces for making transactions including:

Virtual Pool Status - which displays the list of assets for which a particular user has authority (e.g. the assets allocated to a particular division in the case of a division manager) and their availability status (presence in the virtual pool) and which allows the user to carry out transactions to add or to remove assets from the virtual pool;

Hour meter readings - which provides access to provide / correct usage data such as hour meter readings added for the assets for which a particular user has authority (e.g. the assets allocated to a particular division in the case of a division manager);

Online Fomns - which provides access to a plurality of different online forms for requesting fluctuation of a division's asset allocation, for changing/providing division details for which a particular division manager is responsible, for requesting transfer of an asset, and/or for requesting short term hire of an asset.

Asset details interface

The asset details reporting interface is accessible from the reporting interface or, where a link is provided, by clicking on a particular asset number in other reporting interfaces.

On selection of the "Asset Details" report link in the reporting interface a blank asset details report is provided which includes a data entry field that allows entry of an asset identifier (e.g. an equipment number). On submission of a valid asset identifier the asset details report populates with asset details for the asset to which the identifier relates. On selection of a particular asset number in another reporting interface, the asset details report is provided with the asset information already populated.

The asset details report allows the user to view a plurality of different levels of technical asset data by selection of a corresponding tab indicium. On selection of a first tab, a first level of asset data is displayed including for example, where the information is applicable/available: information identifying the asset's manufacturer (e.g. brand information); a capacity that the asset is able to move; the power and/or fuel (e.g. diesel, petrol, electric); a tyre group and/or type; an indication of the presence/absence of various features (e.g. in the case of a lift truck - a load backrest, a side shifter, a fork positioner, or the like); an indicator of the maximum back tilt angle for a lift truck's forks; an indicator of the asset's number of operation stages; details of the power supply for assets requiring electric power (e.g. number of phases, connector type, connector colour etc.); information on the asset's transmission equipment; the asset's towing capacity and/or hitch type; and/or the like.

On selection of a second tab, a second level of asset data is displayed including for example, where the information is applicable/available: a shipment weight of the asset; dimensions of the asset (e.g. equipment width, equipment length, carriage width, maximum/extended height, minimum/lowered/retracted height, free lift height, fork length etc.); the presence/absence of other features (e.g. headlights, tail lights, beacon lights, reverse alarm, fire extinguisher, etc.); an indicator of whether the asset is registered for use on public roads; details of any weather protection (e.g. presence of a cab and/or cab type); and/or the like.

The asset details report also provides a dedicated asset details tab for accessing information for trailer assets. On selection of this tab, asset data is displayed including for example, where the information is applicable/available: trailer dimensions (e.g. bed height, bed length, total length); a trailer capability (e.g. load capacity); a trailer type (e.g. an indication that the trailer is a flat bed trailer); details of the presence/absence of various trailer features (e.g. removable ends, removable sides, road lights, winch brake etc.), details of the trailers body type, front and/or rear hitch type, brake type, steering, number of axels etc.; and/or the like.

The asset details report allows the user to view a plurality of different displays of other asset information, at the same time as the selected technical data, by selection of another corresponding tab indicium as described below. An allocations tab is provided on selection of which historic information is displayed detailing the divisions to which the asset has previously been (and is currently) allocated to, including information identifying the dates of the allocations. A service history (calls) tab is also provided which, when selected, initiates display of the service history for the selected asset including a list of service calls the asset has required and, for each service call, a summary of the reason for the call and/or outcome and the date of each call. A readings tab is also provided which, when selected, initiates display of historic usage data for the asset. Age Profile interface

The age profile reporting interface provides a statistical overview of the age of the assets for which the logged in user is responsible. On selection of the "Age Profile" reporting interface, a chart is displayed which illustrates the number of the assets by year of manufacture and a table is displayed which illustrates the number of assets by age, 'role' (or equipment type/function) identification number and/or name, and location (e.g. a world region such as the UK and/or a district such as the north east).

Service History interface

The service history reporting interface provides a report which allows a user to view all the services history (e.g. pending and previous service calls) for the assets for which the logged in is responsible for or has authority to view.

The service history report allows the user to filter the service history by date range to focus on a particular time period of interest and lists all the service calls for which the logged in is responsible for (or has authority to view) for the selected time period. Each listed service call is provided with a summary of the reason for the call (e.g. fault type), the date of the call/malfunction and date of any resolution, and a summary of the outcome/resolution of the call.

Each listed service call is also provided, where the information is available, with information for identifying of the division to which the asset to which the service call relates is currently allocated (e.g. a division identifier, a name, an address, region, district), technical information (e.g. make and/or model, a capacity that the asset is able to move, power type), and the type of power or fuel required for the equipment (e.g. electric, petrol, diesel etc.).

Allocation list by division interface The allocation list by division reporting interface provides a comprehensive view of the assets for which the logged in user is responsible or has authority to view.

On selection of the "Allocation list by division" a report is displayed which shows a list of the assets for which the logged in user is responsible or has authority to view and a plurality of graphical representations (in this case three) illustrating a breakdown of the listed assets: by manufacturer; by model; and by role type.

For each listed asset there is provided, where the data is available, information for identifying of the division to which the asset is currently allocated (e.g. a name, an address, and/or a division identifier), a 'role' (e.g. equipment type/function) identification number and/or name, an asset identifier, an indication of a date or time frame when the asset was allocated to the division, technical information such as a technical identification code, make and/or model, an asset capability (e.g. a capacity that the asset is able to move), an equipment type indication (e.g. lift trucks, trailer, tow tractor, container handler etc.), the type of power or fuel required for the equipment (e.g. electric, petrol, diesel etc.), and an indication of the date at which the asset entered the pool. Each asset identifier comprises a link which, when accessed initiates a report of the asset details for the asset to which it relates (in effect, it allows a user to "drill down" on to the asset to obtain an asset detail view).

Allocation list by division reporting interface also allows a user to view the graphical representations in a clearer (enlarged) form by selection of an associated "enlarge" indicium (e.g. to follow an associated hyperlink).

Virtual Equipment Pool interface

The virtual equipment pool reporting interface provides a view of assets available in the virtual pool including assets which other fleet divisions have made available. The virtual equipment pool reporting interface may be initiated by selection of a "Virtual Equipment Pool" indicium displayed in the reporting interface.

On selection of the "Virtual Equipment Pool" reporting interface a list of the assets available in the contract pool is provided. For each listed asset there is provided, where the data is available, an asset identifier, an identifier of the division to which the asset is currently allocated, a contract description, current location information, a brief description, an asset capability (e.g. a capacity that the asset is able to move), an equipment type indication (e.g. lift trucks, trailer, tow tractor, container handler etc.), the type of power required for the equipment (e.g. electric, petrol, diesel etc.), and an indication of the date at which the asset entered the pool.

Each asset identifier comprises a link which, when accessed initiates the asset details reporting interface via which the asset details for the asset to which it relates (in effect, it allows a user to "drill down" on to the asset to obtain an asset detail view).

Availability Summary interface

The availability summary reporting interface provides a summary of the availability of the provided assets forming part of the fleet operator's fleet. Late UDR interface

The late UDR reporting interface provides a report of the provided assets for which usage data has not been entered in a current usage data submission period. This is particularly useful because it allows a fleet controller to pursue entry of the required data before closure of a submission window for doing so within the current submission period. If the data is not entered then the usage data for the current period will be estimated (e.g. based on or equal to an average value for other provided assets of a similar type). This is generally undesirable because the use of estimated data can lead to underused or overused assets being overlooked for fleet division transfers or fluctuations. For example, a transfer of an asset from a site/division where the existing assets are underused to a site/division where the existing assets of that type are being overused may be desirable. Similarly, it may also be desirable to exchange an underused asset with an overused asset elsewhere, to return of an underused asset to base, or to acquiring a further asset for a site/division where the existing assets are overused.

Forms overview The asset management tool also provides the ability to generate and progress a plurality of different asset management requests by use of any of a plurality of online forms using the online forms transaction interface. The status of these forms may be tracked using the forms dashboard reporting interface.

The online forms comprise forms for generating various requests including: Fluctuation request - for generating a request for fluctuation of a division's asset allocation (e.g. the provision of a further asset for a particular fleet division in addition to the assets in the current fleet inventory, or the reduction of a fleet division by removal and return to base of a specific asset);

Equipment movement request - for generating a request for transfer of an asset that is available in the virtual pool to a particular fleet division or location;

Short tenv hire request - for generating a request for a short term addition of a further asset for a particular fleet division in addition to the assets in the current fleet inventory;

Change division details request - for generating a request to change the details of the division or divisions for which a particular registered division manager is responsible for (e.g. where the address or other details of a division changes, or where a manager gains responsibility for an additional division, has responsibility transferred to a new division and/or surrenders responsibility of a division).

Forms Dashboard interface The forms dashboard reporting interface provides access to the online forms which the logged-in user has the authority to view. In the case of a division manager, for example, they will typically be provided access to view the forms that they have created whilst a fleet controller (or the members of a fleet control group) will be provided with access to all forms (or a subset of the forms which have been assigned to the logged-in fleet controller for review). The forms dashboard includes a 'Built-in Reporting' section that includes a "Work List" indicium and an "Open Forms" indicium.

When the "Work List" indicium is selected by a user a list is generated which includes all the open requests that have been assigned to, or require action by, the logged-in user (or that have been assigned to a user group to which the user belongs). Typically, therefore, the "Work List" indicium is used by a user, such as a fleet controller, who has the authority/responsibility to review, reject and/or action forms submitted by other users.

When the "Open Forms" indicium is selected a list is generated which includes all the open requests generated by the logged-in user. Typically, therefore, the "Open Forms" indicium is used by a division manager or another user who has submitted an online form, to check the progress of the requests that they have generated.

A filter box is provided in the forms dashboard reporting interface that allows a user to search for specific forms using various filter criteria. A number of examples will now be described, by way of example only, to illustrate the various ways in which a user may filter the information.

It will be appreciated that whilst the filter examples have been described individually the individual filters may be used in combination. In the case of no filters being selected, all the forms that the logged-in user has authority to view will be displayed.

Division Identifier Filter The division identifier filter allows a user to select a particular division to filter on. On selection of a specific division (or selection of divisions), only the forms for the selected division are listed in the result table.

Form Number Filter

When a form is created it is given a unique form identifier (e.g. a numeric or alphanumeric identifier). The filter box allows filtering on this form identification number to display an individual form or, by use of 'wild cards', a group of forms (e.g. having form identification numbers having a common sequence of characters on which the filtering is based).

Form Status Filter The filter box also allows filtering based on the current progress status of the forms through the review and acceptance procedure. Some status types apply to all form types whilst others are form type specific. Form Type Filter

The filter box also allows filtering based on form type (e.g. fluctuation request, equipment movement request, short term hire request, or change details request)

Date Filter The filter box also allows filtering based on the date on which a form was submitted.

A reset indicium is provided to allow a user to reset the filter, to enable a different set of filter choices to be made, by clearing any current filter settings.

Each form listed in the forms dashboard reporting interface are provided with a colour coded ownership indicator which indicates the management entity which has current responsibility for progressing the form further. In this embodiment, for example, the indicator comprises a coloured circle, 'traffic light' or 'dot'. A blue dot indicates that the form is currently assigned to the asset provider for further action, a Yellow dot indicates that the form is currently assigned to the fleet controller (or an associated central management team/fleet control group), a Red dot indicates that the form has been rejected, and a green dot indicates that processing of the form has been completed.

Details of the 'source' division to which the form relates are provided for each listed form and, in the case of a movement request, details of the destination division to which the transfer relates are also provided. Details are also provided, where applicable, of the form type, any asset number referenced during the creation of the form (e.g. the asset requiring transfer), the name or other identifier of the form's creator, the date the form was created, the current 'assignee' or Owner" having responsibility for the current procedural step (e.g. fleet controller/fleet control group/central management team, asset provider, or no-one in the case of a completed or rejected form); a status indication representing the current procedural step of the form (e.g. completed, rejected, pending approval/action by fleet controller, pending approval/action by asset provider); the normal next procedural step in the form's progress; and/or the like.

The forms dashboard reporting interface also allows a listed form to be selected by means of a hyperlink attached to the associated form identifier, and the contents of the form reviewed. Forms may also be printed using the reporting interface be selecting a 'Printable form' indicium provided for the purpose. Selection of the 'Printable form' indicium initiates appearance of a popup window which contains the form in a printable format. From this pop up a user can select a print option to start printing the form. Online Forms interface

The online forms transaction interface enables a user to create and submit forms to generate the associated requests. On selection of the "online forms" transaction indicium provided in the reporting interface, a list of the different types of form is provided (in this embodiment the four types described above). Each listed form type may be clicked by a user to begin the process of completing and submitting a form of that type.

The procedures for creating, submitting and processing each form type will now be described, by way of example only, in more detail with reference to Figures 4 to 7.

Fluctuation Request The fluctuation request form (or a variation of it) is used when a division manager or other authorised user wishes to request an additional asset (including equipment assets such as lift trucks or the like, and attachment assets for use on existing equipment allocated to the division). The fluctuation request form (or a variation of it) is also used when a division manager or other authorised user wishes to reduce / off hire surplus assets (including equipment assets such as lift trucks or the like, and attachment assets for use on existing equipment allocated to the division).

An overview of the procedure followed to generate a request to fluctuate the assets allocated to a particular division or location is shown in Figure 4.

Prior to generating a fluctuation request a division manager can, if the request is for an additional asset, advantageously review the available units in the virtual pool to determine if a suitable asset is available for transfer. Similarly, prior to generating a fluctuation request process a division manager can, if the request is for removal of an asset, place the asset in the virtual pool for a period to provide an opportunity for another division manager to request the unit. Beneficially, this reduces unnecessary return to base and/or transport to client journeys.

In another embodiment the review for suitable assets in the virtual pool, or the making of unwanted assets available in the virtual pool, is advantageously carried out automatically by a fleet management entity when a related fluctuation request is submitted. In this case, if a suitable asset is available in the virtual pool it is transferred to the requesting division in response to a request for an additional asset, rather than supplying a fresh asset. Similarly, if another division requests an asset that is the subject of a remove request it is transferred to that division rather than returning it to base.

As seen in Figure 4 to request a fluctuation the fluctuation request form is first completed and submitted by the applicable fleet manager / user. Fluctuation request - Generation

The fluctuation request form provides data entry fields to allow the user completing the form to select the division to which the request relates. On entry of this information, a plurality of division address fields provided on the form, automatically populate, from an associated database, with the relevant contact/address information for the division to which the form relates.

The fluctuation request form also includes a plurality of sub-location fields for the entry of the address of the site to which the subject asset is to be delivered to, or removed from where this differs from that of the division address as populated in the division address fields. There are also fields for entry of a telephone number and the contact name of an authorised delegate to oversee the delivery/handover of the asset.

A drop down menu is provided for the user to select an associated fluctuation type (e.g. fleet reduction / fleet increase / attachment asset reduction / attachment asset increase).

In response to an indication being made, that the form relates to a fleet increase, further editable fields are provided on the fluctuation request form, as summarised in Table 1.

Field Name Description

MHE The type of asset required.

If this is not known this may be populated accordingly (e.g.

"don't know")

Capacity Required Lift capability (amount of lift the asset needs to meet

requirements).

If this is not known or not applicable the field may be populated with a zero.

Fork Length The length of fork that a lift truck asset will need. Again, If this is not known or not applicable the field may be populated with a zero.

Equipment Power Preferred power type for the asset.

There are three options (in this embodiment), Electric, Diesel and not applicable (although petrol may be an option in other embodiments e.g. for other asset types).

Not applicable may be used for trailer assets.

Upright Type The type of mast the asset will require.

If the asset is a tractor or trailer this may be populated with

"STD".

Load Being Handled Description of the objects being handled. This is free text field, so a short description may be entered with relative ease.

Lift Height Required The maximum height the asset is required to move the handled objects, in millimetres.

If the asset is a tractor or trailer asset this may be populated with a zero to indicate that it is not applicable. Load Dimensions The size of objects to be handled in length, width, and height format.

If this is not known or there is a mixture of handling objects this can be populated accordingly (e.g. 'unsureVvarious'). This can be followed up n a site survey by the asset provider.

Attachment Details of any required attachment.

Required If an attachment is not required this can be populated

accordingly (e.g. not required 'no' or 'not applicable').

Ground Conditions A drop down menu with a list of possible ground conditions to describe the environment/terrain in which the asset is to be used.

Height Restrictions The minimum height which the asset must pass under.

If this is not applicable the field may be populated with a zero.

Application Hazards A drop down menu with a list of potentially hazardous situations to further describe the environment in which the asset is to be used.

Estimated hours of An estimate of the number of hours per month the asset will be work - Per month used.

If the period the asset is required for is less than one month, then the number for estimated hours during the entire hire may be entered.

Justification for The reason why the asset is needed.

Additional Output or This is free text field, so a short justification may be entered with Reduction relative ease.

Qualified operator? A qualified operator is required when using certain types of

asset and this field is used to confirm the presence of such an operator at the delivery site.

Confirm reading and SOP manual sets out roles and responsibilities for all parties. acceptance of The division manager is required to use this field to indicate responsibilities confirmation that the related responsibilities are understood and under standard accepted.

operating

procedures?

Date Required The date when the asset is to be delivered, the date format is

DD.MM.YYYY or a calendar popup is available.

Time Required The time of day (approximate) the asset is required to arrive (in case of preference).

Table 1 - Fleet Increase Fluctuation

In response to an indication being made that the form relates to a fleet decrease further editable fields are provided on the fluctuation request form, as summarised in Table 2.

Field Name Description

Fleet No The asset identification (which is a unique numeric or

alphanumeric identifier provided for each asset by the asset provider) of the asset to be removed from the fleet division.

This is a drop down menu which only lists the assets currently allocated to the division(s) of the logged-in user. This field is

mandatory.

Serial No The serial number of asset (if known). This is an optional field.

Justification for an The reason why the asset is no longer needed.

Additional Output or This is free text field, so a short justification may be entered with Reduction relative ease.

Date Required The date when the asset is to be collected, the date format is

DD.MM.YYYY or a calendar popup is available.

Time Required The time of day (approximate) the asset is required to be

collected (in case of preference).

Table 2 - Fleet Decrease Fluctuation

In response to an indication being made that the form relates to a request for an additional attachment asset for use on another asset (e.g. a vehicle such as a lift truck, tractor, or trailer) a different set of editable fields are provided on the fluctuation request form, as summarised in Table 3.

Field Name Description

Fleet No of main The asset identification of the asset with which the attachment is truck to be used (a unique numeric or alphanumeric identifier provided for each asset by the asset provider).

Serial No The serial number of the asset with which the attachment is to be used (if known). This is an optional field.

Attachment required A field in which the required attachment may be described. This is a mandatory field.

Justification for an The reason why the attachment asset is required.

Additional Output or This is free text field, so a short justification may be entered with Reduction relative ease. This is a mandatory field.

Date Required The date when the attachment asset is to be delivered, the date format is DD.MM.YYYY or a calendar popup is available. This is a mandatory field.

Time Required The time of day (approximate) the attachment asset is required to be delivered (in case of preference).

Table 3 - Attachment Asset Request

In response to an indication being made that the form relates to a request for removal of an attachment asset a different set of editable fields are provided on the fluctuation request form, as summarised in Table 4.

Field Name Description

Fleet No of main The asset identification of the asset with which the attachment is truck being used (a unique numeric or alphanumeric identifier provided for each asset by the asset provider). Serial No The serial number of the asset with which the attachment is being used (if known). This is an optional field.

Attachment required A field in which the attachment being returned is to be described.

This is a mandatory field.

Justification for an The reason why the attachment asset is no longer required. Additional Output or This is free text field, so a short justification may be entered with Reduction relative ease. This is a mandatory field.

Date Required The date when the attachment asset is to be collected, the date format is DD.MM.YYYY or a calendar popup is available. This is a mandatory field.

Time Required The time of day (approximate) the attachment asset is required to be collected (in case of preference).

^" able 4 - Attachment Asset Removal Request

On submission the form is automatically saved and a notification of this is communicated to fleet control (e.g. a fleet controller or a fleet control group/central management team) by email (or other appropriate communication medium) where the request is subject to a preliminary review. After an indication of successful submission is provided and a form history summary is displayed which highlights the procedural stages the form has proceeded through and the current owner (e.g. division control / asset provider).

Fluctuation request - Pending Fleet Control Approval

If the outcome of preliminary review by fleet control is positive the form is approved and a notification to this effect is communicated to the asset provider (e.g. by email). If the result is negative, the request is rejected and a notification to this effect is communicated to the originator of the form with details of the reason for the rejection.

To review the form the fleet controller locates the appropriate form in the forms dashboard report interface and review the request. In the case of a request for an additional asset, the fleet controller reviews the assets in the virtual pool, the asset usage reports and any asset reduction requests made by other divisions. The fleet controller determines, based on this information, if any assets meeting the requirements of the fluctuation request: are available in the virtual pool; are under utilised by another division (whether in the virtual pool or not), or are otherwise surplus to requirements (e.g. the subject of an asset reduction request). In the case of a request for an asset reduction the fleet controller determines if there is a requirement for an asset elsewhere.

Assuming the fluctuation request cannot be fulfilled by transfer of an existing asset of the fleet from/to another division/site preliminary approval of the request is given (subject to any other considerations that may apply). If the fluctuation request can be fulfilled by transfer of an existing asset of the fleet from/to another division/site then the form may be rejected and an indication provided of how the request may be fulfilled, without provision of an additional asset or return of an existing asset, in a comments entry field provided to the fleet controller conducting the review.

In another embodiment, this review and approval process is automated. In yet another embodiment, on determination that the fluctuation request can be fulfilled by transfer of an existing asset of the fleet from/to another division/site, an associated asset movement request is automatically generated for fulfilling the fluctuation request without provision of an additional asset or return of an existing asset.

To provide for the approval, when a fleet controller selects a pending form using the forms dashboard interface a display of a core summary of the information in the form and the forms history to date is provided. A reviewer action area is also provided which includes: a comments entry field to allow the fleet controller to make associated comments (e.g. reasons for approval or rejection). The action area also includes 'approval' and 'rejection' indicia, selection of which will result in the form being approved or rejected respectively. After approval or rejection, the newly entered information is saved and a confirmation is provided that the submission has been successful. On approval by fleet control and communication of the related notification to the asset provider, the process moves to the next procedural step and 'ownership' of the form passes to the asset provider.

Fluctuation request - Pending Asset Provider Approval/Action On receipt of the form the asset provider actions it according to the request. In the case of a request for an additional asset or an additional attachment, if appropriate, the asset provider contacts the originator of the form (if appropriate) to arrange for a site visit in order to survey and qualify the application of the requested asset to allow accurate specification of the most appropriate equipment to perform the task required of the requested asset.

In the case of a request to offer up (return) most assets, the asset provider contacts the originator of the form (if appropriate) to arrange a site visit to inspect the equipment to ensure it is in a fit state to come off contract and that there is no damage to the asset.

In the case of a request to offer up (return) an attachment asset no site visit is organised, and accordingly the asset provider arranges for the attachment to be collected.

In another embodiment, the management of the communication with the originator of the form is automated or semi-automated. For example, emails requesting appropriate information for organising a site visit / collection date (e.g. a request for selection from a choice of dates from an automated diary system) may be sent to the originator automatically and on receipt of correctly formatted replies, a site visit may be automatically diarised. After any inspection / survey has been completed and the requirement qualified (as appropriate) the asset provider provides feedback to the fleet controller to enable them to make a final decision to approve or reject the request. This feedback may, for example, comprise a copy of the equipment survey and equipment / specification recommendation or may comprise asset inspection report highlighting any damage. The feedback may alternatively or additionally comprise comments added to the online form.

On completion of this procedural step, the asset provider "approves" the form which effectively moves the form back to fleet control for a final decision to be made on the request. Exceptionally, the asset provider may "reject" the form, for example if the survey indicates that the application requirements cannot be fulfilled within the terms indicated on the form. The approval/rejection is automatically communicated to the fleet controller and/or Originator ⁵ (if appropriate).

To provide for the approval, when an authorised user of the asset provider selects a pending form for which they are currently responsible, using the forms dashboard interface, a display of a core summary of the information in the form and the forms history to date is provided. A reviewer action area is also provided which includes: a comments entry field to allow the asset provider to make associated comments (e.g. reasons for approval or rejection). The action area also includes 'approval' and 'rejection' indicia, selection of which will result in the form being approved or rejected respectively. Fluctuation request - Pending Fleet Control Approval

On receipt of the notification e-mail, fleet control retrieves the form via the forms dashboard interface for further review in association with any additional information provided by the asset provider. The fleet controller will then consider all the applicable and available information including costs/environmental impact in order to make a decision on the request. Fleet control will then either finally approve or reject the request.

Approval effectively moves the form back to asset provider and initiates an email to notify the asset provider accordingly, whilst rejection terminates the request and initiates an e- mail notification to the originator to inform the originator of the rejection and the reason for it. Fluctuation request - Pending Asset Provider Approval/Action

On receipt of the notification, e-mail by the asset provider, the asset provider actions the request accordingly. For additional equipment or attachment requests, the equipment or attachment will be sourced and arrangements made for their delivery. For the reduction in equipment or attachments, arrangement will be made to collect the equipment or attachments. In one embodiment, management of this stage may be automated or semi-automated. For example, the sourcing of equipment may be automated with by an application accessing an associated sourcing database and the arrangements for delivery/collection may arranged using automated emails requesting appropriate information for organising the collection/delivery and by automatically diarising the collection/delivery on receipt of correctly formatted replies.

Once arrangements for delivery or collection have been made, additional information relating to the arrangements may be populated in fields provided for the purpose in an updated 'action' area of the request form. These fields include: a Carrier Name field for entry of the haulage company name responsible for the transportation, a Vehicle Registration field for entry of the registration details (number plate) of the truck being used to transport the asset; a Driver Name field for entry of the name of the truck driver who will be arriving at the delivery/collection site; Planned Collection/Delivery Date field; and a Planned Collection/Delivery Time field. Once the asset has been delivered or collected, the asset provider will "approve" the form requesting the asset fluctuation, which will result in the form's status changing to "completed" status.

Equipment movement request

The equipment movement request form is completed when a fleet controller or a division manager wishes to request the transfer of an asset from one location to another. The source and destination locations may be locations of the same division or may be locations belonging to different divisions. An overview of the procedure followed to generate a request to move an asset is shown in Figure 5.

Access to the equipment movement request form is provided via the online forms transaction interface as described previously.

Movement request - Generation

Once the movement request form is selected, a blank movement request form is generated. Only a subset of the data fields provided on the form require manual completion initially begin the movement request process. On verification of this manually entered data, many of the other fields are populated automatically. The subset of fields, which can be manually completed initially, are summarised in Table 5.

Field name Description

Incident number A reference number provided by fleet control. It is not a

required field and need only be populated if the reference is available.

Reason for A short description of why the move is required. Movement

Effective Date The date when the equipment is to be transferred.

Fleet number The unique asset identifier of the asset requiring transfer

Table 5 - Asset Movement Request (preliminary data entry fields)

A verification indicium is provided for verifying the initially entered data, selection of which indicium initiates a process to check the validity of the asset number. If the asset number is invalid, an error message is displayed indicating the nature of the error. If the asset identifier is valid, the asset data for the asset to which the identifier relates is automatically populated into associated fields in the movement request form. The fields that are automatically populated in this manner comprise asset details including, for example, make, model, load capacity, asset class, and/or power type (e.g. diesel or electric). The fields that are automatically populated also include information relating to the division and/or location to which the asset is currently allocated including, for example, a division identifier, a division name, and/or division/location address/contact details. The automatic population of these details allows the user to check that the asset that they have identified is correct before processing the remainder of the movement request form. Some of the automatically populated source division/location fields are editable including fields for entry of a contact telephone number and a contact name to allow management of the transfer, at the source end, to be delegated as required.

The movement request form is provided with a destination section for entry of information related to the destination division and/or the destination location for the asset to which the form relates. The destination section provides two options for entering the destination information ('by division' and 'by destination address') which may be selected by corresponding radio button indicia.

Selection of the 'by division' radio button allows manual entry of the division identifier for the destination division and verification of this information. If division identifier is invalid, an error message is displayed indicating the nature of the error.

On successful verification of the division, identifier, address and contact details for the division are automatically populated into other fields provided for this purpose in the destination section of the movement request form. If the division has multiple possible delivery sub-locations, then names or identifiers of the different sub-locations are populated into a drop down menu for selection of the required delivery address. On selection of the desired delivery address, the address and contact fields populate or re- populate automatically in accordance with the selected sub-location. Some of the newly populated destination fields are editable including fields for entry of the contact details to allow management of the transfer, at the destination end, to be delegated as required.

Selection of the 'by destination address' radio button allows manual entry of destination (i.e. delivery) address details. This is particularly useful as it provides flexibility for transfers to a location which either does not form part of an existing division (e.g. to allow transfer to a temporary work site) or for which the division identification details are not known.

The fields provided on selection of the 'by destination address' radio button are summarised in Table 6.

Table 6 - Asset Movement Request (destination data entry fields)

On submission of the movement request form, confirmation is provided that it has been saved successfully and a form history table is generated and displayed which details the date the form was created and its progress through the review procedure. The history table includes details of who is currently responsible (the form 'owner') for the next stage in the procedure.

A notification of the submission is automatically communicated to fleet control (e.g. a fleet controller or a fleet control group/central management team) by email (or other appropriate communication medium) where the movement request is subject to a preliminary review. Movement request - Pending Fleet Control Approval

A user from fleet control (e.g. a fleet controller) then reviews the submitted movement request, using the forms dashboard interface, for validity and completeness and to determine if the movement can be fulfilled internally. Assuming the movement request cannot be more efficiently fulfilled internally, preliminary approval of the request is given (subject to any other considerations that may apply). If the movement request can be fulfilled internally, then the form may be rejected and an indication to this effect entered in a comments entry field provided to the fleet controller conducting the review.

If the outcome of preliminary review by fleet control is preliminary approval, then the form is approved and a notification to this effect is communicated to the asset provider (e.g. by email). If the result is negative, the request is rejected and a notification to this effect is communicated to the originator of the form with details of the reason for the rejection.

In another embodiment this review and approval process is automated based, for example, on acceptance criteria provided in an associated database. In yet another embodiment, on determination that the movement request can be fulfilled internally the transfer is organised and actioned by fleet control. Where the transfer is organised and actioned by fleet control, management of the transfer may be automated or semi- automated. For example, the arrangements for delivery/collection may arranged using automated emails requesting/providing appropriate information from/to the source and destination contacts and appropriate service providers (e.g. a haulage company) to organise the collection and delivery; and by automatically diarising the collection and delivery on receipt of correctly formatted replies.

To provide for the approval, when a fleet controller selects a pending form using the forms dashboard interface a display of a core summary of the information in the form and the forms history to date is provided. A reviewer action area is also provided which includes: the comments entry field to allow the fleet controller to make associated comments (e.g. reasons for approval or rejection). The action area also includes 'approval' and 'rejection' indicia, selection of which will result in the form being approved or rejected respectively. After approval or rejection, the newly entered information is saved and a confirmation is provided that the submission has been successful. On approval by fleet control, and communication of the related notification to the asset provider, the process moves to the next procedural step and 'ownership' of the form passes to the asset provider.

Movement request - Pending Asset Provider Approval/Action On receipt of the form, the asset provider actions it according to the request. The asset provider will review the request. The review involves locating the asset to which the request relates (by means of the asset identifier) in an associated inventory and determining the transfer requirements accordingly (e.g. the type of equipment, load weights, transfer distance, and any other influencing factors - for example use of cranes). The asset provider prepares an estimated cost and/or environmental impact of the requested transfer. The estimated cost/impact is entered into the form prior to form submission. It will be appreciated that this process may be manual or may be automated, in dependence on requirements and complexity of the movement request.

On completion of this procedural step, the asset provider "approves" the form, which effectively moves the form back to fleet control for a final decision to be made on the movement request. Exceptionally, the asset provider may "reject" the form, for example if the transfer requirements cannot be fulfilled due to technical, geographic, and or other constraints. The approval/rejection is automatically communicated to the fleet controller and/or 'originator' (if appropriate).

Movement request - Pending Fleet Control Approval

On receipt of the notification e-mail, fleet control retrieves the form via the forms dashboard interface for further review in association with the additional cost/impact information provided by the asset provider. The fleet controller will then consider all the applicable and available information including the costs/environmental impact in order to make a decision on the request. Fleet control will then either finally approve or reject the request. Approval effectively moves the form back to asset provider and initiates an email to notify the asset provider accordingly, whilst rejection terminates the request and initiates an e- mail notification to the originator to inform the originator of the rejection and the reason for it.

Movement request - Pending Asset Provider Approval/Action On receipt of the notification e-mail by the asset provider, the asset provider actions the request by making the arrangements necessary for collection, transportation and delivery of the asset.

In one embodiment, management of the transfer may be automated or semi-automated. For example, the arrangements for delivery/collection may arranged using automated emails requesting/providing appropriate information from/to the source and destination contacts and appropriate service providers (e.g. a haulage company) to organise the collection and delivery; and by automatically diarising the collection and delivery on receipt of correctly formatted replies.

Once arrangements for delivery and collection have been made, additional information relating to the arrangements may be populated in fields provided for the purpose in an updated 'action' area of the request form. These fields include: a Carrier Name field for entry of the haulage company name responsible for the transportation, a Vehicle Registration field for entry of the registration details (number plate) of the truck being used to transport the asset; a Driver Name field for entry of the name of the truck driver who will be arriving at the delivery/collection site; Planned Collection/Delivery Date field; and a Planned Collection/Delivery Time field.

Once the asset has been transferred, the asset provider will "approve" the form requesting the movement, which will result in the form's status changing to "completed" status.

Short term hire request form The short term hire request form is typically completed when a division manager wishes to request a further asset in addition to current fleet inventory, but only for a short term period. An overview of the procedure followed to generate a request to move an asset is shown in Figure 6.

Access to the short term hire request form is provided via the online forms transaction interface as described previously.

Short term hire request - generation

Once the short term hire request form is selected an associated blank form is generated. The short term hire request form is provided with a drop down list of division identifiers from which the user generating the request can select the division to which the request relates. A second drop down list, of sites/geographic locations or sub-locations associated with the selected division is also provided, from which the location/sub- location requiring delivery can be selected.

On selection of a location/sub-location, the address and contact information is automatically populated into address/contact fields provided for the purpose on the form. In case the location for delivery is not present in the second drop down list (e.g. because the location is a temporary work site or the like), a further section is provided including further address/contact fields which may be completed manually as appropriate.

A further data entry section is provided for entry of the details relating to the asset being requested. The data entry fields provided in this section are summarised in Table 7.

Field Name Description

MHE The type of asset required.

If this is not known this may be populated accordingly (e.g.

"don't know")

Capacity Required Lift capability (amount of lift the asset needs to meet

requirements).

If this is not known or not applicable the field may be populated with a zero.

Fork Length The length of fork that a lift truck asset will need. Again, If this is not known or not applicable the field may be populated with a zero.

Equipment Power Preferred power type for the asset.

There are three options (in this embodiment), Electric, Diesel and not applicable (although petrol may be an option in other embodiments e.g. for other asset types).

Not applicable may be used for trailer assets.

Upright Type The type of mast the asset will require.

If the asset is a tractor or trailer this may be populated with

"STD".

Load Being Handled Description of the objects being handled. This is free text field, so a short description may be entered with relative ease.

Lift Height Required The maximum height the asset is required to move the handled objects, in millimetres.

If the asset is a tractor or trailer asset this may be populated with a zero to indicate that it is not applicable.

Load Dimensions The size of objects to be handled in length, width, and height format.

If this is not known or there is a mixture of handling objects this can be populated accordingly (e.g. 'unsureTvarious'). This can be followed up n a site survey by the asset provider.

Attachment Details of any required attachment.

Required If an attachment is not required this can be populated

accordingly (e.g. not required 'no' or 'not applicable').

Ground Conditions A drop down menu with a list of possible ground conditions to describe the environment/terrain in which the asset is to be used.

Height Restrictions The minimum height which the asset must pass under.

If this is not applicable the field may be populated with a zero.

Application Hazards A drop down menu with a list of potentially hazardous situations to further describe the environment in which the asset is to be used.

Estimated hours of An estimate of the number of hours per month the asset will be work - Per month used.

If the period the asset is required for is less than one month, then the number for estimated hours during the entire hire may be entered.

Initial Hire Period The required Hire Period

Justification for The reason why the asset is needed.

Additional Output or This is free text field, so a short justification may be entered with Reduction relative ease.

Qualified operator? A qualified operator is required when using certain types of asset and this field is used to confirm the presence of such an operator at the delivery site.

Confirm reading and An SOP manual sets out roles and responsibilities for all parties. acceptance of The division manager is required to use this field to indicate responsibilities confirmation that the related responsibilities are understood and under standard accepted. operating

procedures?

Date Required The date when the asset is to be delivered, the date format is

DD.MM.YYYY or a calendar popup is available.

Time Required The time of day (approximate) the asset is required to arrive (in case of preference).

Table 7 - Requested Asset Details

On submission of the short term hire request form, confirmation is provided that it has been saved successfully and a form history table is generated and displayed which details the date the form was created and its progress through the review procedure. The history table includes details of who is currently responsible (the form Owner') for the next stage in the procedure.

A notification of the submission is automatically communicated to fleet control (e.g. a fleet controller or a fleet control group/central management team) by email (or other appropriate communication medium) where the short term hire request is subject to a preliminary review.

Short term hire request - Pending Fleet Control Approval

A user from fleet control (e.g. a fleet controller) then reviews the submitted short term hire request, using the forms dashboard interface, for validity and completeness.

The fleet controller also reviews the assets in the virtual pool, the asset usage reports and any asset reduction requests made by other divisions. The fleet controller determines, based on this information, if any assets meeting the requirements of the short term hire request: are available in the virtual pool; are under utilised by another division (whether in the virtual pool or not), or are otherwise surplus to requirements (e.g. the subject of an asset reduction request). Assuming the short term hire request cannot be fulfilled by temporary transfer of an existing asset of the fleet from another division/site, preliminary approval of the request is given (subject to any other considerations that may apply). If the short term hire request can be fulfilled by transfer of an existing asset of the fleet from another division/site, then the form may be rejected and an indication provided of how the request may be fulfilled, without short term hire of an additional asset, in a comments entry field provided to the fleet controller conducting the review.

In another embodiment, this review and approval process is automated. In yet another embodiment, on determination that the short term hire request can be fulfilled by short term transfer/loan of an existing asset of the fleet from another division/site, an associated asset movement request is automatically or manually generated for fulfilling the movement request without hire of an additional asset. If the outcome of preliminary review by fleet control is preliminary approval, then the form is approved and a notification to this effect is communicated to the asset provider (e.g. by email). If the result is negative, the request is rejected and a notification to this effect is communicated to the originator of the form with details of the reason for the rejection. In another embodiment, this review and approval process is automated based, for example, on acceptance criteria provided in an associated database.

To provide for the approval, when a fleet controller selects a pending form using the forms dashboard interface a display of a core summary of the information in the form and the forms history to date is provided. A reviewer action area is also provided which includes: the comments entry field to allow the fleet controller to make associated comments (e.g. reasons for approval or rejection). The action area also includes 'approval' and 'rejection' indicia, selection of which will result in the form being approved or rejected respectively.

After approval or rejection, the newly entered information is saved and a confirmation is provided that the submission has been successful. On approval by fleet control and communication of the related notification to the asset provider, the process moves to the next procedural step and 'ownership' of the form passes to the asset provider.

Short term hire request - Pending Asset Provider Approval/Action

On receipt of the form the asset provider will review the request and action it accordingly. The review involves reviewing the type of asset request and determining the transport requirements accordingly (e.g. the type of equipment, load weights, transfer distance, and any other influencing factors - for example use of cranes). The asset provider prepares an estimated cost and/or environmental impact of the requested hire, including daily/weekly short term hire rates for the requested item in addition to the estimated transport cost.

The estimated cost/impact information is entered into the form prior to form submission. It will be appreciated that this process may be manual or may be automated, in dependence on requirements and complexity of the request.

On completion of this procedural step, the asset provider "approves" the form, which effectively moves the form back to fleet control for a final decision to be made on the request. Exceptionally, the asset provider may "reject" the form, for example if the transfer requirements cannot be fulfilled due to technical, geographic, and or other constraints. The approval/rejection is automatically communicated to the fleet controller and/or 'originator' (if appropriate). Short term hire request - Pending Fleet Control Approval

On receipt of the notification e-mail, fleet control retrieves the form via the forms dashboard interface for further review in association with the additional cost/impact information provided by the asset provider. The fleet controller will then consider all the applicable and available information including the costs/environmental impact and any alternatives for meeting the request, in order to make a final decision on the request. Fleet control will then either finally approve or reject the request.

Approval effectively moves the form back to asset provider and initiates an email to notify the asset provider accordingly, whilst rejection terminates the request and initiates an e- mail notification to the originator to inform the originator of the rejection and the reason for it.

Short term asset - Pending Asset Provider Approval/Action

On receipt of the notification e-mail by the asset provider, the asset provider actions the request by making the arrangements necessary for transportation and delivery of the asset.

Once the asset has been delivered, the asset provider will "approve" the form requesting the hire, which will result in the form's status changing to "completed" status.

Change division details request form

The change division details request form is typically completed when a division manager (or their alternate/deputy) wishes to notify a change of division details, for example, where a new division/location/sub-location needs to be set up, where an existing division/location/sub-location ceases to be used, where address or contact details change, where the division or divisions for which the division manager (or their alternate/deputy) is responsible changes, or the like. An overview of the procedure followed to generate a request to move an asset is shown in Figure 7.

Access to the change division details request form is provided via the online forms transaction interface as described previously.

Change division details request generation

Once the change division details request is selected, an associated blank form is generated. The change division details request form is provided with a drop down list of division identifiers from which the user generating the request can select the division to which the request relates. A second drop down list, of sites/geographic locations or sub- locations associated with the selected division is also provided, from which a location/sub-location can be selected. The form also includes a plurality of checkboxes which allow the user to select from a plurality of reasons for the requested change. These checkboxes comprise check boxes for each of the following change reasons: the division address or contact information is changing; the division manager or deputy is changing; the division is being disbanded; and/or a new division is being added.

Selection of each checkbox results in the display of an associated data entry section for adding/modifying the associated details. On submission of the change division details request form, confirmation is provided that it has been saved successfully and a form history table is generated and displayed which details the date the form was created and its progress through the review procedure. The history table includes details of who is currently responsible (the form Owner') for the next stage in the procedure. A notification of the submission is automatically communicated to fleet control (e.g. a fleet controller or a fleet control group/central management team) by email (or other appropriate communication medium) where the short term hire request is subject to a preliminary review.

Change division details request - Pending Fleet Control Approval A user from fleet control (e.g. a fleet controller) then reviews the submitted change division details request, using the forms dashboard interface, for validity and completeness.

Assuming the change division details request is acceptable, approval of the request is given (subject to any other considerations that may apply). Otherwise, the form may be rejected. If the outcome of preliminary review by fleet control is preliminary approval then the form is approved and a notification to this effect is communicated to the asset provider (e.g. by email). If the result is negative, the request is rejected and a notification to this effect is communicated to the originator of the form with details of the reason for the rejection. In another embodiment, this review and approval process is automated based, for example, on acceptance criteria provided in an associated database.

To provide for the approval, when a fleet controller selects a pending form using the forms dashboard interface a display of a core summary of the information in the form and the forms history to date is provided. A reviewer action area is also provided which includes: the comments entry field to allow the fleet controller to make associated comments (e.g. reasons for approval or rejection). The action area also includes 'approval' and 'rejection' indicia, selection of which will result in the form being approved or rejected respectively. After approval or rejection the newly entered information is saved and a confirmation is provided that the submission has been successful. On approval by fleet control and communication of the related notification to the asset provider the process moves to the next procedural step and Ownership' of the form passes to the asset provider.

Change division details request - Pending Asset Provider Approval/Action On receipt of the form, the asset provider will review the request and action it accordingly by updating the master data stored for the division in accordance with the request.

On completion of this procedural step the asset provider "approves" the form resulting in the form's status changing to "completed". Exceptionally, the asset provider may "reject" the form, for example if there are logical inconsistencies in the proposed modification to the division details.

Virtual Pool Status interface

The Virtual Pool Status transaction interface enables a user such as a division manager to tag assets in the fleet division for which they are responsible as being available for reallocation to other fleet divisions (or reallocation to other locations within the current division).

On selection of the "Virtual Pool Status" transaction in the reporting interface a list of the assets that the logged-in user an asset list is provided which includes all the provided assets for which the logged in user has authority. For each listed asset an "in Pool" selection indicium such as a flag or 'check-box' is provided which indicates the current virtual pool availability status (e.g. "in pool" = checked/flagged and "not in pool" = unchecked/unflagged). The "in Pool" selection indicium may thus be selected to indicate that the asset is not currently required and is therefore available in the virtual pool of available assets, or de-selected to indicate that the asset is currently required and is therefore no longer available in the virtual pool of available assets. Once an asset, or plurality of assets have been selected and/or de-selected the user can submit the changes by clicking on a submission indicium (e.g. a graphically represented 'button') to save the changes and refresh the list accordingly.

Each asset in the list is also provided, where the data is available, with an asset identifier, an identifier of the division to which the asset is currently allocated, a contract description, current location information, a brief description, an indication of the date at which the asset entered the pool (where applicable), a asset capability (e.g. a capacity that the asset is able to move), an equipment type indication (e.g. lift trucks, trailer, tow tractor, container handler etc.), and the type of power required for the equipment (e.g. electric, petrol, diesel etc.)

Hour Meter Readings interface (UDRS) The hour meter readings transaction interface is used to record usage data such as hour meter readings on a periodic submission basis (typically monthly, weekly, or every other week). The transaction is accessed by selecting an "Enter Hour Readings" indicium provided via the reporting interface.

On selection of the hour meter readings transaction interface, an asset list is provided which includes all the provided assets for which the logged in user has authority (e.g. the assets allocated to a particular division in the case of a division manager). Data entry fields are provided for the submission of hour meter data subject to appropriate data constraints such as a newly entered hour meter reading being within certain defined limits (e.g. the newly entered reading being greater than a previously submitted reading). After submission of the newly entered hour meter reading by clicking a "SUBMIT" indicium (e.g. a graphic button or the like) the report refreshes, the submit indicium disappears and a "SAVED" indicium appears in its place to indicate that the data has been updated.

Each asset in the list is also provided, where the data is available, with an asset identifier, a brief description, location information, a division identifier, an indication of the submission period to which the previous reading relates, the previous reading (estimated or previously submitted), an indication of the submission period to which a newly entered reading will relate, and/or an indication of whether or not usage data may be entered (e.g. an indication of whether or not the current date is within the current periods submission window).

The hour meter readings interface also allows the newly entered data to be updated by re-selecting the "Enter Hour Readings" transaction, which results in the transaction refreshing into a state where the data can be entered. The entry and update of the hour meter data may be subject to constraints on when it may be entered. The entry is restricted to an appropriate submission time window within each submission period, for example a submission window between the 1 ^st and 15 ^th of the month (in the case of a monthly submission period). When a submission window has expired, any usage data submitted during the submission window is finalised as the usage data recording for the submission period in which it was entered. The hour meter readings interface also allows download of a data file (e.g. a spreadsheet file) comprising a list of all the equipment in the users asset list that can be used by the user for the entry of usage data. This is particularly beneficial in the case of data entry where the number of assets for which usage data is required is relatively large.

Modifications and alternatives

A detailed embodiment has been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above embodiments whilst still benefiting from the inventions embodied therein.

In the above embodiment, a number of modules were described for convenience. As those skilled in the art will appreciate, where all or part of the module's functionality is provided in software, the software may be provided in compiled or un-compiled form and may be supplied as a signal over a computer network, or on a recording medium. Part or all the functionality performed by the modules may be performed using one or more dedicated hardware circuits, but the use of software modules is preferred as it facilitates the updating of the management interface to update module functionalities. It will also be appreciated that the functionality of the modules may not be provided in discernable discrete modules but may be provides in any suitable way.

Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

In another embodiment, the asset management tool provides the division manager / fleet controller with a transaction for generating an exchange request for exchanging similar assets between sites. This exchange request may, for example, be used to exchange vehicles having different usage patterns and/or service histories to allow usage to be averaged out over a plurality of assets thereby limiting wear and tear on the assets and reducing the frequency of service/maintenance calls.

In another embodiment, the asset management tool provides the asset provider with access to a 'super pool' comprising the assets available in the virtual pools of several different fleet operators to which they supply assets. Where a request for provision of an asset can be fulfilled more efficiently from the super pool than from fresh supply an associated transfer is organised using the asset management tool to process a 'super pool' transfer request through an approval process to gain approval for the transfer from fleet control of at least the supplying fleet operator, and possibly the fleet control of the receiving fleet operator. As part of the approval process, the service history, usage history and/or other technical information relating to the asset may be provided to a receiving fleet controller to allow assessment of potential maintenance problems prior to approval. Each feature disclosed in this specification (which term includes the claims) and/or shown in the drawings may be incorporated in the invention independently (or in combination with) any other disclosed and/or illustrated features in the same or another embodiment. In particular but without limitation the features of any of the claims dependent from a particular independent claim may be introduced into that independent or another independent claim in any combination or individually.

The text of the abstract filed herewith is repeated here as part of the specification. In an exemplary aspect of the invention of the invention there is provided method of managing provision of physical assets to an asset user. The method comprises initiating physical provision of a plurality of assets to an asset user for use at a plurality of different geographic locations. An inventory of provided assets for said asset user is maintained and an interface is provided for use by the asset user to manage said plurality of assets. The interface provides means for generating a request for transfer of a provided asset from its respective location to another specified location and means for generating a request for supply of a further asset in addition to the current inventory. On receipt of a request generated using said interface, for an asset having a required capability at a specified location physical transfer of a provided asset from its respective location to the specified location or physical supply of a further asset, in addition to the provided assets in the current inventory initiated accordingly.