WO2010037175A1

WO2010037175A1 - Hazardous goods tracking system

Info

Publication number: WO2010037175A1
Application number: PCT/AU2009/001308
Authority: WO
Inventors: John Vincent Moore
Original assignee: Global Tracking Solutions Pty Ltd
Priority date: 2008-10-01
Filing date: 2009-10-01
Publication date: 2010-04-08

Abstract

A method of tracking at least part of the life cycle of a hazardous goods item (204) is disclosed. The method comprises providing a data storage device (22) arranged to store a plurality of records, each record being associated with a hazardous goods item (204) and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item. The method also comprises facilitating receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices (28), and populating the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices (28). A data repository used in the method and a corresponding system for tracking dangerous goods items is also disclosed.

Description

Hazardous Goods Tracking System

Field of the Invention

The present invention relates generally to a hazardous goods tracking system and to a method of tracking hazardous goods.

Background

It can be desirable to track items from manufacture to use and/or disposal or for parts of the journey of the items. This is particularly desired for dangerous goods, such as explosives.

Summary of Invention

According to a first aspect of the present invention there is provided a method of tracking at least part of the life cycle of a hazardous goods item, said method comprising: providing a data storage device arranged to store a plurality of records, each record being associated with a hazardous goods item and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item; facilitating receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices; and populating the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices.

In one arrangement, the multiple distributed data gathering devices are respectively disposed at at least two of a manufacturing facility, a packaging facility, a storage facility, a transportation device, and a usage location. In one embodiment, the life cycle data comprises data associated with a plurality of a manufacturing stage in a life cycle of an item, a packaging stage in the life cycle of an item, a transportation stage in the life cycle of an item, a storage stage in the life cycle of an item, and a usage stage in a life cycle of an item.

In one embodiment, the method comprises disposing a machine readable item tag on the hazardous goods item, the item tag including a machine readable item identifier usable to distinguish the item from other items.

In one embodiment, the method comprises using the item identifier to associate the item with a record in the data storage device, and when the item identifier is read by an item tag reader, identifying the record associated with the item, and adding received life cycle data to the identified record.

In one embodiment, the item tag comprises a RFID item tag, and at least one of the data gathering devices comprises a RFID reader.

In one embodiment, the method comprises placing at least one item in a package and disposing a machine readable package tag on the package, the package tag including a machine readable package identifier usable to distinguish the package from other packages. The machine readable package tag may comprise a package RFID tag.

In one embodiment, the method comprises adding a package identifier associated with a package containing an item to a record associated with the item when the package identifier is read by a package tag reader.

In one embodiment, at least one of the data gathering devices comprises a data entry device usable to facilitate manual entry of life cycle data.

In one embodiment, at least one of the data gathering devices comprises at least one sensor. In one embodiment, at least one of the data gathering devices comprises a positioning device such as a GPS device or a device arranged to provide survey point information.

In one embodiment, at least one of the data gathering devices comprises a timing device arranged to provide timing information usable to time stamp communications to the data storage device.

In one embodiment, the method comprises forwarding stored life cycle data particular to a stage in a life cycle of an item to the data storage device when the item identifier is read at the stage.

The life cycle data associated with a manufacturing stage may comprise information indicative of the manufacturing facility, the type of item, how the item was manufactured, the components used to manufactured the item, when the item was manufactured, and/or who was involved in manufacture of the item.

The life cycle data associated with a packaging stage may comprise information indicative of the packaging facility, the type of package, the number of items contained in the package, how items are packaged, when items were packed, and/or who packed the items in the package.

The life cycle data associated with a storage stage may comprise information indicative of the storage facility, when an item or package was transferred to the storage facility, who was involved in receiving the item or package on arrival at the storage facility, whether the item or package is returned from a usage stage, and/or who was involved in dispatching the item from the storage facility.

The life cycle data associated with a transportation stage may comprise information indicative of a transportation device, where an item or package is being taken from, where an item or package is being taken to, when the item or package was loaded onto the transportation device, when the item or package arrives at a destination, and/or who conducted the transportation.

The life cycle data associated with a usage stage may comprise information indicative of a usage location, when an item is used, and/or who used the item.

In one embodiment, the method comprises facilitating receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item through the Internet.

In one embodiment, the data storage device comprises a database, which may be a relational database.

In one embodiment, the method is arranged to facilitate retrieval of selected data from the data storage device by a user, for example through the Internet.

The method may comprise providing different levels of access to data stored in the data storage device, and assigning one of the levels of access to each user authorised to access the data storage device.

In one embodiment, the method comprises securing communications to and from the data storage device. In one arrangement the communications are secured using a public/private key regime, by encrypting the communications, by requiring a user to enter a password and/or a username, by providing a user with an electronic key generation device, by obtaining biometric information from a user, and/or using digital certificates.

In one embodiment, the method comprises disposing a replacement item tag on an item if a previous item tag is damaged or has been inadvertently removed, and adding a replacement tag identifier to the record associated with the item so as to link the new identifier to the record associated with the previous identifier. In one embodiment, the hazardous goods items comprise an explosive item, a detonator, a propellant, pyrotechnics, munitions, or a dangerous chemical/material.

According to a second aspect of the present invention there is provided a data repository for tracking at least part of the life cycle of a hazardous goods item, said data repository comprising: a data storage device arranged to store a plurality of records, each record being associated with a hazardous goods item and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item; the data repository being arranged to: facilitate receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices; and to populate the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices.

According to a third aspect of the present invention there is provided a system for tracking at least part of the life cycle of a hazardous goods item, said system comprising: a data repository having a data storage device arranged to store a plurality of records, each record being associated with a hazardous goods item and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item; and a plurality of distributed data gathering devices arranged to gather life cycle data indicative of at lest part of the life cycle of the item; the data repository being arranged to: facilitate receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from the multiple distributed data gathering devices; and to populate the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices.

In accordance with a fourth aspect of the present invention, there is provided a computer program which when loaded into a computing system causes the computing system to operate in accordance with a data repository for tracking at least part of the life cycle of a hazardous goods item, said data repository comprising: a data storage device arranged to store a plurality of records, each record being associated with a hazardous goods item and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item; the data repository being arranged to: facilitate receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices; and to populate the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices.

In accordance with a fifth aspect of the present invention, there is provided a computer readable medium having a computer program stored thereon which when loaded into a computing system causes the computing system to operate in accordance with a data repository for tracking at least part of the life cycle of a hazardous goods item, said data repository comprising: a data storage device arranged to store a plurality of records, each record being associated with a hazardous goods item and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item; the data repository being arranged to: facilitate receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices; and to populate the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices.

Brief Description of the Accompanying Drawings

In order to provide a better understanding of the present invention, various embodiments will be described in more detail, by way of example only, with reference to the accompanying drawings, in which:

Figure 1 is a schematic block diagram of a system for tracking hazardous goods according to an embodiment of the present invention; Figure 2 is a schematic block diagram of a data repository of the system shown in Figure 1 ; Figure 3 is a schematic flow chart illustrating a method of tracking hazardous goods according to an embodiment of the present invention; Figure 4 is a schematic block diagram illustrating a tracking process wherein a first stage in the life cycle of an item is tracked using the system shown in Figure 1 ; Figure 5 is a schematic block diagram illustrating a tracking process wherein a second stage in the life cycle of an item is tracked using the system shown in Figure 1 ; and Figure 6 is a schematic diagram illustrating the content of data storable in an

RFID tag used in an embodiment of the present invention.

Description of Example Embodiments

Referring to the Figures, a hazardous goods tracking system 10 is shown which comprises a data repository 12 accessible on-line from a remote location through a communications network, in this example the Internet 24.

In one embodiment, the data repository 12 is implemented using a computing device, for example a personal computer shown in more detail in Figure 2. The personal computer 12 comprises a data storage device 22, a processor 50, an input 52, an output 54, and a working memory 56. The working memory 56 may comprise random access memory (RAM), EEROM, flash memory or other suitable form of memory. The processor 50 is operatively connected to the input 52 and the output 54, typically via a bus. The data storage device 22 is arranged to store data indicative of a hazardous goods item including data indicative of at least part of the life cycle of the item. While the present data storage device 22 is locally disposed relative to and forms part of the computing device 12, it will be understood that the data storage device 22 may be local, external or networked relative to the processor 50. The data storage device may include one or more actual or logical data storage devices.

The processor 50 is controlled to operate in accordance with one or more computer programs, which typically are resident during use in the working memory 56, the programs enabling the data repository to receive data indicative of a dangerous goods item and associated information relevant to the life cycle of the item, and to coordinate storage of the data in the data storage device 22 and retrieval of data from the data storage device 22, as further described below.

In the example shown in Figure 1 , the data repository 12 is connected through the Internet 24 to a data collecting system. The data collecting system comprises a plurality of data collecting devices, 26A, 26B₁ two of which are shown in Figure 1. In this example, each data collecting device 26A, 26B is connected to at least one data gathering device 28.

In this example, the data repository 12 is accessible through the Internet 24 by a client device 32, which may be for example a personal computer, a portable or handheld computing device, a PDA, or a mobile communications device such as a mobile telephone. In this example, the client device 32 is in the form of a personal computer and accordingly comprises a display 34 for displaying information to a user and user input devices 36, such as a keyboard and a mouse, and/or a touch screen. Each of the data gathering devices 28 is arranged to gather data associated with a hazardous goods item and, in association with a respective data collecting device 26, is arranged to forward the gathered data to the data repository 12 for storage in the data storage device 22. However, instead of forwarding gathered data through a data collecting device 26, data gathered by the data gathering devices 28 may be forwarded directly to the data repository 12.

Each hazardous goods item to be tracked by the present system 10 is provided with a machine readable tag, for example which has been applied to the item by a manufacturing facility. In the present example, the machine readable tag is an RFID tag which is readable using a suitable RFID reader, although it will be understood that other types of machine readable tag are envisaged, such as bar codes. The important aspect is that the tag has a unique identifier associated with it which can be read using a machine and which can be used to identify the item.

In this example, the data storage device 22 is implemented in the form of a relational database, with each item having one record or several linked records in the database. During the life cycle of a hazardous goods item, information relevant to the life cycle, such as data associated with manufacture, storage, transportation, and usage of the item, is gathered using the data gathering devices 28, and the gathered data is forwarded to the data storage device for populating in the relevant record(s) in the database 22.

The data is stored in the database so that a user may retrieve the history or part of the history of the item by entering an appropriate query. Furthermore, where items have information in common such as, for example, they are packaged together in an identifiable package, suitable relational links can be made between the items.

After application of a tag to an item, information indicative of the unique identifier associated with the item is stored in a new record in the database 22 and serves as a primary key for the record. Further information indicative of the item, or indicative of the life cycle of the item such as any subsequent transportation of the item, storage in magazines, or usage of the item is then added to the record so that the life history of the item is stored in the database 22 for subsequent review by a user.

The record associated with an item is populated by providing data gathering devices 28 at multiple locations in an expected life cycle of a hazardous goods item, at least some of the data gathering devices comprising a scanning device arranged to read machine readable tags and thereby retrieve at least the unique identifier from the tag so that the relevant record in the database 22 can be identified. The data gathering devices 28 may also be arranged to gather other information relevant to the item such as when the item was made, transported or stored; where the item was stored or transported from or to; who manufactured, transported, or handled the item; when, where and by whom the item was used; and so on. This may occur by providing the data gathering devices 28 with a data entry terminal usable by an operator at the data gathering device 28 to enter the information; by automatically identifying persons using, handling, manufacturing or transporting the item, such as by providing these persons with machine readable tags which contain unique identifying information, for example disposed on a wristband; and/or by storing information at a facility, such as a manufacturing, transporting or storage facility, which identifies the facility, and which is automatically forwarded to the database 22 with the unique tag identifier for addition to the relevant record in the database 22.

Typically, the data collecting devices 26 are remotely located from the data repository 12. As such, communications between the data collecting devices 26 and the data repository 12 may be susceptible to interception, and in this embodiment the authenticity of a data collecting device 26 is established by encrypting communications between the data collecting device 26 and the data repository 12, for example using a public/private key regime, using digital certification, and so on.

Similarly, communications between a client device 32 and the data repository 12 may be secured by encrypting the communications between the data collection device 26 and the data repository 12, for example using a public/private key regime, using digital certification, and so on.

Referring to Figure 3, a flow diagram 100 is shown which illustrates a general process for populating the database 22 and retrieving information from the database 22.

In order to add data associated with an item to the database 22, data is gathered 110 from a data gathering device 28 and the gathered data is forwarded 112 to a data collecting device 26 associated with the data gathering device. The gathered data is then forwarded 113 to the data repository 12 and the processor verifies that the data collecting device 26 is authorised to communicate with the data repository 12 or verifies that the communication is authorised, for example using public/private key authentication, or digital certification. The data repository 12 then locates 116 the relevant record associated with the gathered data using the unique identifier associated with the item, and adds 118 the gathered data to the record.

Once the data is stored in the database 22, it is accessible to an authorised user. In order to retrieve data from the database 22, a user is first identified 120 at a client device 32, for example by entering a login name and password. Additional levels of security may be required such as verifying a biometric reading taken from the user with a reference biometric reading of an authorised user, for example stored in the database 22. In addition or alternatively, an electronic key generated by a device known to be associated with the authorised user may be provided to data repository 12 for verification.

A query for data particular to one or more hazardous goods items can then be put 122 to the data repository 12 by a client and the processor 50 of the data repository 12 interprets the query and retrieves 124 the requested data from the database 22. The retrieved data matching the query is then provided 126 to the user by providing it to the client device 32, for example by displaying the retrieved data on the display 34. In addition or alternatively, the retrieved data may be forwarded to the user in hard copy.

Figure 4 shows in schematic form a first stage in the life cycle of an item from manufacture of the item to storage of the item in a magazine prior to usage of the item, for example in a magazine associated with a user organisation.

In this example, the machine readable tags 202 are RFID tags comprising a radio frequency identification chip. As part of the manufacturing process, a RFID tag 202 is affixed to an item 204 after the item has been manufactured. Attaching the RFID tag 202 to the item allows the item 204 to be uniquely identified using a unique identifier (typically a number) stored in the tag 202. The identifier can be read by a data gathering device 262 located at the manufacturing facility, in this example an RFID reader which is in range of the RFID tag 202. The identifier and information indicative of the manufacturing facility are then sent to the data repository for storage in the relevant record in the data repository identified using the identifier associated with the item. Typically the RFID tag 202 will be attached to an item 204 during or after manufacture of the item 204 at a manufacturing facility. A tagged item is indicated in Figure 4 by reference numeral 204'.

In this example, additional information relating to manufacture of the item 204 is gathered at the manufacturing facility using a data gathering device 264 which may include a computing device arranged to permit manual entry of information by a user, one or more sensors and/or a scanning device arranged to scan machine readable tags such as RFID tags. This information may comprise, for example, information indicative of the type of item, how the item was manufactured, the components used to manufactured the item, when the item was manufactured, and who was involved in its manufacture. The additional information is sent to the data repository for storage in the relevant record associated with the item in the data repository.

In this embodiment, one or more tagged items 204' are placed into a package 208. A package may for example comprise a box, a bag, roll, reel or container into which one or more items are placed for transportation. The package is preferably also tagged with a machine readable tag 206, which may also be a RFID type tag and which also has a unique identification code. The tagged package is indicated in Figure 4 by reference numeral 208'. The identification number of the tag 206 serves to identify the package 208', and at some stage during or after the packaging stage, the tag 206 is scanned by a data gathering device 266, in this example a RFID reader, and information indicative of the package is sent to the data repository 12 for storage in the relevant record(s) associated with the item(s) contained in the package 208'.

In this example, additional information relating to packaging of the item 204 is gathered at a packaging facility using the data gathering device 266 which may further include a computing device for manual entry of information by a user, and one or more sensors. This information may comprise, for example, information indicative of the type of package 208', the number of items 204' in the package 208', how the items 204' are packaged, when they were packed, where they were packed and who packed them. The additional gathered information is sent to the data repository 12 for storage in the relevant record associated with the item.

Instead of using an RFID tag, another type of machine readable identifier could be used, such as a barcode, or any other suitable machine readable device that enables the package to the uniquely identified.

After the package has been filled with items, the package 208' is weighed using a scale 210, and details of the weight of the package are gathered using a data gathering device 268 and sent to the data repository 12 for storage in the appropriate record associated with the item. The data gathering device 268 may be arranged to automatically derive weight information directly from the scale 210. A plurality of packages 208' may then be stacked on a pallet, and the packages 208' stored in a first storage place 212.

On arrival at the first storage place 212, the package RFID tag 206 is scanned using a data gathering device 270, in this example an RFID reader, and information indicative of the first storage place 212 is sent to the data repository 12 for storage in the relevant record associated with the item so as to indicate that the package 208' has arrived at the first storage place 212.

One or more of the packages 208' may be subsequently transported by a transportation vehicle 214 (for example a truck) from the first storage place 212 to a second storage place 216.

On leaving the first storage place 212, the package RFID tag 206 is rescanned using the data gathering device 270 and information is sent to the data repository for storage in the relevant record associated with the item so as to indicate that the package 208' has left the first storage place 212.

In this example, additional information relating to handling of the item at the first storage place is gathered at the first storage place 212 using the data gathering device 270 which may further include a computing device for manual entry of information by a user, and one or more sensors. This information may comprise, for example, when the package was transferred to the first storage place 212, who was involved in receiving the item at the first storage place 212 and who was involved in dispatching the item from the first storage place 212.

When the package 208' is loaded onto the transportation vehicle 214, the package RFID tag 206 is scanned using a data gathering device 272 and information indicative of the transportation vehicle 272 is sent to the data repository 212 for storage in the relevant record associated with the item so as to indicate that the package 208' has been loaded onto the transportation vehicle 214.

In this example, additional information relating to transportation of the item at by the transportation vehicle is gathered using the data gathering device 272 which may further include a computing device for manual entry of information by a user, and one or more sensors. This information may comprise, for example information, as to where the items are being taken from, where they are being taken to, when they were dispatched, when they arrived at the destination and who conducted the transportation.

On arrival at a second storage place 216, the package RFID tag 206 is scanned using a data gathering device 274, in this example an RFID reader, and information indicative of the second storage place 216 is sent to the data repository 12 for storage in the relevant record associated with the item so as to indicate that the package 208' has arrived at the second storage place 216.

In this example, additional information relating to handling of the item at the second storage place 216 is gathered using the data gathering device 274 which may further include a computing device for manual entry of information by a user, and one or more sensors. This information may comprise, for example, when items arrive at the storage place 216, and information similar to the information gathered at the first storage place 212.

It will be understood that the first storage place 212 may be a magazine of a manufacturer and the second storage place 216 may be one of many magazines associated with users of hazardous goods items.

One or more computing devices may be provided to control and coordinate operation of the data gathering devices 262, 264, 266, 268, 270, 272, 274.

It will be understood that the data gathering devices may include any device arranged to generate or facilitate generation of data to be included in a record at the data repository. For example, the data gathering devices may include scanning devices arranged to read information from machine readable tags, computing devices arranged to facilitate manual entry of information by a user, and one or more sensors for measuring/receiving information related to the life cycle of hazardous goods items including manufacture, transportation, storage and handling of the items. The data gathering devices may also include GPS devices arranged to provide positional information, other devices arranged to generate survey point information, and/or timing devices arranged to generate timing information, for example so that all or some of the communications between the data gathering devices 28 and the data repository 12 are time stamped.

It will also be understood that the system may be arranged to write data to the machine readable tags, for example by including such functionality in one or more of the data gathering devices. The data written to a machine readable tag may be the same as or a subset of the data gathered by a data gathering device and sent to the data repository 12 for inclusion in a record. Such write functionality may be incorporated into one or more of the data gathering devices 28, into one or more of the data collecting devices 26, or a separate data writing device may be provided.

It will also be understood that the unique identifier of each tag 202 functions as the key in the database 22 and is therefore included in the communications between the data gathering devices and the data repository 12 so that the relevant record in the database 22 can be identified.

In one embodiment, the unique identifiers associated with several machine readable tags may be forwarded to the data repository prior to manufacture of items, so that records associated with the identifiers may be created at the database 22 in advance. The identifiers may be allocated to particular types of items, such as for example explosives, detonators, and so on, and may be marked as such in the tags and thereby in the database 22.

Package identifiers associated with the package tags 206 attached to the packages 208 may also be sent to the data repository prior to attachment of the package tags 206 to the packages 208. In this way, the data repository need only associate a package identifier with one or more item identifiers in the database record structure in order to capture the packaging status in the life cycle record of an item. As with the item identifiers, the package identifiers may be allocated to particular types, such as for example explosives, and may be marked as such in the package tags. This information may be stored in the package tags 206 to indicate the intended use of the package tags 206. This has an additional advantage in that tracking of a tag 204/206 that is yet to be attached to an item or package is possible, for example if an unattached tag is found.

Figure 5 shows in schematic form a second stage in the life cycle of an item from storage of the item in the second storage place 216 to usage of the item by a user. In this example, the items are explosives and a user desires to receive and use multiple explosives as part of a mining operation.

On leaving the second storage place 216, the package RFID tag 206 is scanned using the data gathering device 362 and information indicative of the second storage place 216 is sent to the data repository 212 for storage in the relevant records associated with the items contained in the package so as to indicate that the package 208' has left the second storage place 216.

In this example, additional information relating to handling of the item at the second storage place is gathered at the second storage place 216 using the data gathering device 362 which may further include a computing device for manual entry of information by a user, and one or more sensors. This information may comprise, for example, when the package was dispatched from the second storage place 216, who was involved in dispatching the item from the second storage place 216, the intended use for the items, the intended user of the items, and where the items are to be used.

It will be understood that in circumstances wherein not all items in a package are desired to be used, instead of scanning and identifying a package 302, individual items may be scanned and data relating to these items sent to the data repository 12 for storage in the relevant records.

At an intended work site, the explosive items 304 may be arranged in a blasting pattern 306 with one or more of the items being inserted in corresponding holes 308 according to conventional blasting techniques, and the explosive items detonated 310 so as to loosen the surrounding material. Some of the items 304' or packages 2087302 removed from the second storage place 216 and provided to the user may ultimately not be used and are returned to the second storage place 216. A partly used returned package is indicated in Figure 5 by reference numeral 302'. Any unused items 304' and/or full or partly full packages 302' which are returned to the second storage place 216 are scanned using the data gathering device 362 and information indicative of the second storage place 216 is sent to the data repository 212 for storage in the relevant record associated with the item so as to indicate that the package 208' has returned to the second storage place 216.

In this example, additional information relating to returning of the item to the second storage place is gathered at the second storage place 216 using the data gathering device 362. This information may comprise, for example, when the items/packages are returned, why they are returned, and who returned them.

It is envisaged that in some circumstances the identification tag 202 may be inadvertently removed from the item 204' or may become damaged. If this occurs a new identification tag 312 may be attached to the item. The newly tagged item is indicated in Figure 5 by reference numeral 314. The new tag 312 is scanned using a data gathering device 366 and information indicative of the tag is sent to the data repository for storage in a relevant record associated with the item. In order that the full life cycle of the item may be present in the data repository, a relationship is created in the database 22 between the record associated with the new tag and the record associated with the previously removed or damaged tag.

Similarly, in some circumstances the identification tag 206 attached to the package 302 may be inadvertently removed from the package 302 or may become damaged. If this occurs a new identification tag 316 may be attached to the package. The newly tagged package is indicated in Figure 5 by reference numeral 318. The new tag 316 is scanned using a data gathering device 368 and information indicative of the tag is sent to the data repository for storage in the relevant record(s) associated with the item(s) stored in the package. In order that the full life cycle of the items in the package may be present in the data repository, a relationship is created in the database 22 between the record associated with the new tag and the record associated with the previously removed or damaged tag.

In other instances, the item 204' may be actively destroyed because it is defective or contaminated. The process of recording the destruction may be similar to that of recording usage, but may also include other information, such as who authorised the destruction, who conducted the destruction, and where and when the destruction occurred. This information may be gathered by any suitable data gathering device and a similar process to the above described process whereby a defective tag is replaced carried out.

One or more computing devices may be provided to control and coordinate operation of the data gathering devices 362, 364, 366, 368.

As with the data gathering devices shown in Figure 4, it will be understood that the data gathering devices shown in Figure 5 may include any device arranged to generate or facilitate generation of data to be included in a record at the data repository. For example, the data gathering devices may include scanning devices arranged to read information from machine readable tags, computing devices arranged to facilitate manual entry of information by a user, and one or more sensors for measuring/receiving information related to the life cycle of hazardous goods items including manufacture, transportation, storage and handling of the items. The data gathering devices may also include GPS devices arranged to provide positional information, other devices arranged to generate survey point information, and/or timing devices arranged to generate timing information, for example so that all or some of the communications between the data gathering devices 28 and the data repository 12 are time stamped.

In order to facilitate gathering of information which identifies a person involved in manufacture, storage, transportation, handling or usage of an item or a package, each person may be assigned a unique personal identifier, in this example stored on a RFID tag worn or carried by each person. For example, each person may wear a wrist band having an RFID chip embedded therein which serves to identify the person when the RFID chip is read by a data gathering device.

The system may be arranged so as to restrict access to items and/or packages to authorised personnel only. For example, the data repository may record data indicative of authorised and non-authorised people by marking unique personal identifiers associated with the people so as to indicate authorised or non-authorised status for various manufacturing, handling, transportation, storage and usage actions. When a person handles a restricted item or accesses an area in which restricted items are kept, the personal identifier is read using a data gathering device and a check is made to the data repository to verify that the proposed action to be carried out by the person is authorised.

It will be understood that the present system is arranged to store detailed information relating to the life cycle of hazardous goods items from manufacture to usage and, accordingly, using the present system it is possible for a person to obtain information relating to the history of an item should it be necessary. For example, relevant authorities may wish to track the progress of certain types of dangerous goods such as explosives. Importantly, should an item such as an explosive item be found and the history of the item is not apparent, the historical life cycle of the item can be obtained by extracting data from the relevant record in the database which is associated with the tag attached to the item.

The system may be arranged such that multiple levels of access to the data stored at the data repository are available for allocation to users. For example, authorised personnel could have selected read/write and/or print privileges to selected data or access to all data stored in the data repository 12. In one arrangement, people associated with manufacturers may only be allowed to access information relating to the manufacture, packaging, transportation and delivery of their own products. Mine operators may only be allowed access to data relating to movement, handling and usage of items particular to the mine operators. An authorised user may access the stored data using the client device 32, or any other suitable communications enabled device.

In an embodiment, the databank 22 may be operated as a part of or associated with an administration computer system of a business such as a mining company, or may be independent of any user of hazardous goods items.

A simple example of a suitable database structure, in particular showing the structure of data stored in a record or one or more linked records associated with an item, is set out below.

Identification I Information Type I Data

ID Manufacture

I I- What

I 1- Where

I I- When

I I- Who

Package

(Repackage)

I- Identifier

I 1- Type

1- Where

1- When

I- Who

Storage

I- Where When in When out Who in

I- Who out

Transport

Where from Where to When leave When arrive Who

Use

What When

I- Where

Reapply

New Identification

Destroy

Where When Why Who

Each piece of information (under the heading Data) is grouped into an information type (under the heading Information Type), typically according to each distinct stage in the history of a tag, that is, a manufacturing stage, packaging stage, storage stage, transportation stage, usage stage, tag reapplication stage, and/or a destroy stage.

In one embodiment, the information recorded about the item in the database 22 comprises one or more of the following: the type and specifications of the item; the name of the manufacturer and an identification of the manufacturing facility where the item was manufactured; a list of the components used to manufacture the item; an identifying reference to a person or identifying references to persons involved in manufacture of the item; the time of manufacture of the item; an identifying reference to the package that the product is placed in; the number of items in the package; a list of items in the package; the time and/or date of packaging the item; the weight of the item; and a batch number of a batch of items manufactured.

In an embodiment, information about the item is recorded on the identification tag 202. The information may comprise one or more of the following: the type of item; the weight of the item; a time and/or date of manufacture of the item; an identifier of the manufacturer of the item; an identifying reference to a person or identifying references to persons involved in manufacture of the item.

At a later time this information can be read from the relevant machine readable tag, in this example a RFID tag 202, and can be compared to the information stored in the databank 22. This may occur automatically each time the RFID tag 202 is read or it can be instigated manually.

In an embodiment, information about the items in a package is recorded on a package tag 206. The information may comprise one or more of the following: a list of items in the package; an identifying reference to a person or identifying references to persons involved in manufacture of each item; the type of item; the nominal weight of each item; a batch number the items; a Material Safety Data Sheet (MSDS).

In an embodiment, information about the package is recorded on the package tag 206. The information may comprise one or more of the following: an identifying reference to a person or identifying references to persons involved in packing the items into the package; the date of packaging; the time of packaging; the number of items in the package; the weight of the package; the form of packaging; a batch number.

At a later time this information can be read from the RFID tag 206 and can be compared to the information stored in the database 22. This may occur automatically each time the RFID tag 206 is read or it can be instigated manually.

In an embodiment, details of the arrival of an item or a package are compared to stored dispatch details. This allows tracking of each item or each component used in each item and each package to occur at an individual unit level. If required this will allow transportation details of items or components to be traced back to a supplier.

In an embodiment, the information recorded in the databank 22 can be used to conduct a risk analysis. An alarm may be raised in the event that a high level of risk is found in the risk analysis. The risk assessment is typically conducted by providing a set of rules and testing a set of circumstances against the rules. If the conditions specified in a rule are met then a risk level is present that causes the generation of an alarm. The alarm may be categorised. The alarm may cause a warning to be displayed/sounded and a report on the cause of the alarm to issue. In an embodiment, the risk analysis comprises one or more of the following: determining whether a person having performed a particular task is authorised to perform the task; determining whether a component used in the manufacture of the item is appropriate; determining whether a combination of components used in the manufacture the item is appropriate; determining whether the weight of an item is appropriate; determining whether the weight of a package is appropriate.

In an embodiment, the information recorded in the database can be used to produce a report of the items manufactured or subsequently handled. In an embodiment, the report includes one or more of the following: the items manufactured and the associated identifying references to the items; the packaging of the items and the associated identifying references to the packages; the identifying references of the items contained in a package; the date, time of manufacture or packaging; the identity of people involved in manufacturing, packaging or handling of one or more items or packages; the current location of an item or package; the identification of a person who is recoded as being in custody of an item or package; the chain of custody of an item or package.

Secure access to information stored in the database 22 can be achieved by use of security protocols. An electronic key generator device 38 may be required, which is interfaced to the client device 32. The device electronic key generator 38 may comprise a serial (eg USB) or other communication interface which facilitates transfer of a password and/or encryption key generated by the device 38 to the client device 32 in order to authenticate the user of the client device 32 to the data repository 12. However, it will be understood that secure access to the data in the database may be achieved in any suitable way.

An aspect of the security protocol is to issue each company/organisation with a login number which is combined with the password output by the electronic key generator device 38. Thus an electronic key generator device 38 can only be issued to an authorised organisation. The login number and/or password can be linked to a user identification for each person authorised by an organisation so that access to the organisation's electronic key generator device(s) 38 can be controlled.

In order for an organisation to be issued with an electronic key generator device 38, one example would be for the organisation to apply to a controlling entity for an account, and if accepted the organisation would be supplied with one or more electronic key generator devices 38. In order to be authorised for an account information such as organisation name, company registration number, factory/explosives location, contact details, dangerous goods license number and explosives storage number may be required. The organisation may need to reregister periodically, for example annually. The organisation may need to register for each country/state/region in which it operates.

Authorised users may be sponsored by a registered organisation. A nominated administrator may be responsible for registration and sponsorships issued by the organisation. For example, a shotfirer may be issued with a user identification if requested by the sponsoring registered organisation. The organisation may be responsible for verifying information related to the sponsored user is correct. Such information may comprise the person's name, date of birth and place of birth, along with either an approved shotfirer number or Security Restricted Substance (SRS) number or equivalent, and a passphase. An identity check may be required. The data repository 12 may issue a unique shortfirer ID number for each registered shotfirer. For purposes of this specification, a shotfirer is a person authorised to sell, use, or handle explosives. In an embodiment, once a user identification has been approved there need not be an on-going relationship between the sponsor and the shotfirer; the user identification may be portable with the shotfirer so that it can be used anywhere around the world. If the shotfirer forgets his/her number he/she can log into the data repository 12 using the approved organisation's electronic key generator device 38 and enter identifying information, and the data repository 12 will advise the organisation, such as via email, of the shotfirer's user identification.

If a shotfirer moves to another country and is employed by another organisation in the other country, an administrator of the other organisation can log onto the data repository and request the shortfirer's user identification, which will be given once required information is provided. The data repository 12 can advise the administrator of the shotfirer's user identification. The administrator can then log the shotfirer onto the organisation's database as an employee.

When a person accesses the data repository, an identification of the organisation that the user is from and the user identifier of that person are recorded in the databank 22 along with time and date of the access.

Example

The present invention has particular application to manufacture and handling of dangerous goods such as explosives and similar combustibles and energetic substances such as propellants and pyrotechnics, although it can be used for other hazardous goods items, such as munitions, and other dangerous chemicals/materials. The example below describes the present invention used in relation to explosive items, and in particular to tracking the life cycle of explosive items.

In the present example the machine readable tags used to track the life cycle of the explosive items are in the form of RFID tags, each RFID tag including a data space into which data may be electronically stored. In order that all RFID tags are readable and data stored in the tags can be understood, it is preferred that the data space of each of the RFID tags is formatted to a common standard, such as the inventor's "RFID - Explosives Tracking Code (ETC) protocol". The RFID - ETC protocol 1102 defines how sections of the data space in the RFID chip are used and an example is shown in Figure 6.

The first section of the data space includes information inserted by the RFID chip supplier 1104. This will include an 8 byte unique identification number (UID) 1106 as well as control and write access information. In the 17th to 20th bytes data corresponding to the type of item is recorded 1108, in this example the letters "EXPL" since the item to receive the RFID tag is an explosive item. The second section includes information about the manufactured explosive 1110 and can be inserted by the explosives manufactuer. This includes, for example, a number assigned under the United Nations system of codifying dangerous goods 1112, a country code which is assigned to the country of manufacture 1114, a manufacturing plant number (which is, for example, assigned by a government agency) 1116, a product code or material number 1118, a batch number 1120, a serial number 1122, a net explosive quantity (NEQ) 1124, the number of units in a package 1126 (or 1 is the RFID chip is attached to a single unit), extra support data 1128 which can be used, for example, to convey other information from the manufacturer, and a unit identification number 1130. The unit identification 1130 comprises the date of manufacture 1132, a packaging type 1134, a product type contained in the packaging 1136, and a label/manufacturing identification number 1138. In this case, the packaging type will be coded for 'box' as the explosives are in a box type of package. Other types of package could include unit, roll, palette, bag, container, bin, package, coil, bundle, bottle or tank. The third section has a free data space 1140. The fourth section is for an electronic signature 1144, for example including an identification number of the person manufacturing or packaging the explosives or checking explosives out of a magazine, such as a shotfirer. Reading the fourth section of the RFID chip will reveal the identity of the last authorised person to handle the explosive item during the manufacturing process or the person that received the dispatch of the manufactured explosive, or the person that removed the explosive from a storage place, provided that data indicative of the identity of the person is written to this data block as part of a handling process. This can serve as an electronic proof of delivery (EPOD) which is recorded on the RFID tag, but also sent to and recorded in the database 22.

Certain parts of the data space are locked on manufacture of the RFID chip such as the UID. The control and write access information is used for this purpose. The "EXPL" data is locked when the RFID tag is allocated for use with explosives. Other parts can be locked or left rewritable according to the needs of the manufacturer. It will be common for details relating to the nature of the product/package to be locked after manufacture/packaging. Other details related to the handling of the item/package may be left unlocked.

The UID in combination with the date of manufacture provides a unique identification of the item/package when the RFID tag is attached to the item/package. This unique identification is written to the RFID tag by a RFID label printer. A number or code can be assigned to each RFID tag printer in the individual manufacturing section or by product type.

Example codes used in the RFID-ETC protocol are:

AN a

Boosters b Cartridge c

Detonator d

Exploding cord e

Other explosives f

Non RFID supplied product or replacement tag applied 0 Reserved for military use 1-9

If a shotfirer removes explosives to be used in the field the relevant EPOD identification of the shotfirer ID will be recorded in the databank 22. It is desirable for each identification tag to be recorded in the database 22 when the identification tag is sent to the manufacturer of the item. This allows the recorded life cycle of each item's tag to commence at the start of the chain of custody.

An RFID tag manufacturer preferably supplies the data repository 12 with every RFID-ETC UID number and where possible details of the relevant explosives manufacturer. This is entered into the database 22. The data gathering device 262 of the explosives manufacturer logs each RFID-ETC number and sends them to the data repository for recording in the database 22 both on arrival and also when placed on an item or on a containment device/package (cartridge, roll, box, pallet).

The information sent to the data repository may comprise: a. Tag's UID number b. UN Product number c. Country of manufacturing d. Manufacturing plant ID e. Package Tag ID

This allows the data repository to record information on which tags have been deployed and on what type of explosives.

The data gathering device 270 of the magazine at the manufacturer's plant records movement into and out of its magazine and this data is sent to the data repository 12 for recording in the database 22.

The information sent to the data repository may comprise: a. Magazine management system ID number b. Location number c. Person's ID number d. Date and time e. Tags UID number f. UN Product number g. Country of manufacturing h. Manufacturing plant ID i. Package Tag ID

This allows the data repository 12 to record further information in a tag record already within the database 22 related to the initial storage of the explosives.

The data gathering device 272 of a transport company also logs loading and movement of the explosives using the RFID-ETC UID. This data is sent to the data repository 12 for recording in the database 22.

The information sent to the data repository may comprise: a. Magazine management system ID number b. Location number c. Person ID number d. Date and time e. Tags UID number f. UN Product number g. Country of manufacturing h. Manufacturing plant ID i. Package Tag ID j. Transfer location number

This allows the data repository to record further information in a tag record already within the database 22 related to the transportation of the explosives.

Upon receipt by another magazine and when booked out the magazine data receiving device 274/362 logs this information and sends it to the data repository 12 for recording in the database 22.

The information sent to the data repository may comprise: a. Magazine management system ID number b. Location number c. Person's ID number 32 d. Date and time e. Tags UID number f. UN Product number g. Country of manufacturing h. Manufacturing plant ID i. Package Tag ID

This allows the data repository 12 to record further information in a tag record already within the database 22 related to the storage of the explosives at a user's site, eg a mine site.

When a person books out RFID-ETC explosives in the approved manner the person's user identifier is stored on the RFID tag by the magazine management system and this action is recorded within the magazine management system. When the magazine management system connects with the coordinator all explosive movements are logged into the database, including the user identification of the person removing the explosives. The same user identification can be used by the coordinator as the user identification of the organisation's magazine management system so that the user identification in both systems is consistent.

When the shotfirer loads the explosives into the respective holes 308 this is logged by the data gathering device 364 and sent back to the data repository for recording in the database 22.

The information sent to the data repository 12 may comprise: a. Tracking system ID number b. Location number c. Person's ID number d. Date and time of transaction e. Tags UID number f. UN Product number g. Country of manufacturing h. Manufacturing plant ID i. Package Tag ID j. Transaction position (eg GPS position or survey location) k. Type of transaction that triggered sending the information

This allows the data repository 12 to record further information in a record already within the databank 22 related to the usage of the explosives.

Each employee is given an employee number when they become employed by a manufacturer. This may be issued by the data repository and recorded in the database 22. This number can be used as the identifying reference for the employee. The number can be installed on the RFID tag associated with the employee, such as on a wrist band. The personalised RFID tag can used for both access and process control. The RFID tag would also have the person's own private access ID number that may be required when logging onto the system or equipment or allowing access to restricted areas. This could result in the manufacturer being able to identify which person put a particular product into a box, which weighing scale was used and at what time, as part of the QA/QC process. This number can be recorded by the data repository 12 in the database 22 or issued by the data repository 12 and recorded in the database 22.

Some items may have more than one identifier associated with them. For example, an RFID tag may be installed in a rubber seal used to manufacture a detonator. The identification of the seal is logged with the identification of the detonator. Thus the detonator will have two identifications associated with it. Both identifications can be read and recorded in the databank 22.

Data received from a data collecting device 26, at least some of which is derived from the data gathering devices 28 associated with the data collecting device 26, is forwarded by the data collecting device 26 to the data repository 12 and stored in the database 22. The data repository 12 may cross reference each RFID tag dispatched from the manufacturing plant with those received by the magazine management system. A risk analysis may be conducted to check if the items sent match the items that arrive. The data repository 12 can also provide reports back to the manufacturer on data that it has been sent to allow cross checks of the manufacturing data against data received.

Data on a RFID tag attached to an explosive device may comprise manufacturing company name, contact details of the manufacturer, information about the product, safety information, handling instructions, purchase order number, name of the customer, location of the customer, date of manufacture, NEQ, product weight, box weight, UN number, government information, shipping information, Hazchem information, quantity, layers, packaging data etc. The RFID tag may be embedded in a sticky label that can be printed in colour / with colour codes.

The database 22 may be arranged so that it is structured primarily around the RFID ETC UID Number (REUN) of the identification tag attached to the item and or package. Other data is associated with the REUN. An example of other data related to the REUN could be:

• Location, Date, Company the tag was made • Date/time tag sent out

• Location, manufacturer's name tag sent to

• Date/time tag placed into explosives

• Location, Date, Explosives booked into magazine and by whom

• Stock take - Location, Date and by whom • Location, Date, Explosives booked out of magazine and by whom

• Location, Date, Explosives sent to and support info (pit five, blast 7 east)

• Location, Date, Explosives received and by whom

• Location, Date, Explosives sent to magazine • Location, Date, Explosives booked into magazine and by whom

Location can be made up of both a name or reference number and a GPS coordinate. A person will use his electronic device to login to the user's account. Once the identity of the user is confirmed a number of options are available. Below are some examples:

1) Modified company data a) Administrator b) Add i) New Operation ii) Magazine locations (Northing/Easting) iii) Personnel c) Deactivate i) Magazine locations (Northing/Easting) ii) Personnel 2) Log data a) Shift data

3) Review data a) REUN b) Approved company c) Approved personnel d) Movements e) Stock location f) Stock levels g) Risk alerts h) Log data entry

4) Upload data a) Approved personnel b) Movements c) Stock location d) Stock levels e) Risk alerts f) Log data entry

5) New account a) Company b) Administrator c) Person

Online access may provide limited automatic authorisation to information. Some information may not be available on-line and/or may require manual authorisation to allow access to certain information.

Reports may be compiled from data sent from a data collection device 26 in the form of a magazine management system to the data repository and saved in the database 22. These reports can be generated automatically or upon request by a user of client device 32. Automatic reports can be generated periodically or when certain conditions are met. Example reports are: a. Tag printed by unit, batch, date, time, ID numbers, NEQ, number of units etc.; b. The operator using RFID tag printer and date/time; c. Amount of tags printed off compared to the number tags being recorded against product; d. The number of tags against product type of size/length/weight; e. The time taken to load a box with explosives; f. The batch number e.g. of explosives, plastic units or boxes used; g. RFID tag numbers; h. The number of RFID tags placed onto product for trial or quality assurance/quality compliance purposes; i. RFID Tag numbers of product that went into a non full or non standard box; j. Cycle time of a product through the production process; k. Information from each weighing scale;

I. Information on who was working where and for how long m. Net Explosives Quantity (NEQ) within the magazine; n. Volume of product by unit type; o. Explosives movement into and out of the magazine; p. Stock returns; q. Out of hours access; r. Amount of explosives used and type; s. Trial and/or damaged products; t. Transfers; u. Delivery times; v. Shift, daily, weekly monthly, quarterly and year; w. Risk alerts /red flags generated by whom and when, while; x. Date of Manufacture (DOM) of products by type; y. Movement of explosives to what location and form what location

(for example what dangerous goods were checked into the magazine and by whom, what dangerous goods were checked out of the magazine and by whom, and what goods were returned to the magazine and by whom); and z. Stock out reports.

It will be appreciated that the number and type of reports that can be produced is not limited to this list.

Example of Package Level Tracking

A shortfirer books out one box of 32x 200 package cartridge emulsion and uses 20 out of 200 cartridges. The box is wet and falls apart.

a) The tag is good, however the box is unserviceable. The explosives (180 cartridges) are removed and placed into another box. Depending on the desired operation the new box may be untagged or already tagged. If untagged it can be tagged with a new RFID tag. If already tagged the existing tag could be overwritten, reallocated to the contents of the old (untagged) box or the old tag destroyed and the box retagged. The new tag can be linked to the of tag identification of the old tag.

b) The tag is unserviceable however the box is good. The old tag is destroyed and a new RFID tag is attached to the box and linked to the old tag identification. 01308

38

Example of Unit Level Tracking

A shortfirer books out a full box of 32x 200 package cartridge emulsion and uses 20 out of 200 cartridges.

a) The tag and the box are still good. Due to the box being opened the box label will be identified as semi active in the system. Semi active means that units can be linked to the box as a means of transport device. If some of the explosives (100 cartridges) are placed in another box and then the other semi active box will be linked to the cartridges in the database. When a box is opened the number of items in the box can be stored on the RFID tag and when items are removed or added the contents of the box may be updated.

b) The tag is good however the box is unserviceable. The package tag will be identified as semi active in the database. A clean box can be used to hold the explosives and a new tag attached to the box. The cartridges are linked to the semi active tag on the box.

Risk alerts can be determined from data compiled or data sent from a data collection device 26 in the form of a magazine management system or field system for the use of items to the data repository and saved in the database 22. A risk is determined to exist when one or more factors meet certain criteria, in which case an alert is raised. Typically those possible adverse occurrences which have a high to certain likelihood and moderate to catastrophic consequences trigger an alert. For example alerts can be generated if one or more of the following occurs:

Scanning more explosives out of a box than it can hold; Scanning the same box or units twice; Scanning boxes or units back in that have not being booked out;

Old stock in a magazine not being removed; Moving product to a non approved location; and Exceeding the magazine NEQ limits. The data from scanning items/packages delivered can be compared to the data provided with the delivered goods to verify on-site that all the sent goods have arrived and are checked into the magazine. This can also be further checked off-side and independently verified by the data repository.

An expiry date can be recorded with each item and the expiry data monitored to ensure expired items are not used. The expiry date of closed packaged items may differ from the expiry date of items of an opened package. For example the expiry date of a sealed box of explosives may be four years, whereas the expiry date of each unit of explosives inside the box may only be two years once the box is opened.

A report can be produced by the data repository 12 on when items will expire.

Tracking the inventory of items within the magazine can also be useful for stock control. A manager of the storage facility can determine when certain items are in need of the ordering. Furthermore, the ordering process can be automated such that when certain items drop to a threshold, an automatic order can be generated for more. The inventory tracking can be conducted by the data repository 12 which can keep track of the inventory of many storage facilities to assist in their stock replacement.

Stock usage may be communicated to the distributor/manufacturer's/user's computer which maintains relevant records of delivery and stock levels, and when stock level reaches a specified level the computer can automatically initiate an order for stock

The stock level can be determined according to a usage rate, lead time to manufacture and/or delay in delivery. The usage rate may be entered according to planed consumption. Alternatively the usage rate is calculated based on typical historic usage rates.

If an item, such as an explosive device, is found by relevant authorities outside of an authorised place such as outside of a mine site or its magazine, the RFID tag on the item can be read to obtain its associated identifier, and the relevant record in the database 22 consulted to determine who was last in control/custody of the explosive and where it was from.

The data repository 12 may receive a request from an approved Government body to track an RFID tag. This could be the result of stolen explosives or just stolen tags. The data repository 12 can place a trace on the tag/tags and once the tags were identified an alert can be generated. The alert may trigger sending of an email to an approved person.

The data repository 12 could also directly send out RFID tag identification codes or other data so that the identification code or other data is encountered on or in relation to an item then an alert can be generated. An example of this would be if a shotfirer's name was of interest and this was linked to a particular items or items. The data repository 12 could send out a look out request to all registered users to be on the lookout for these tags. This could be where explosives were being transported or stored in and around approved locations, where an EXPL warning program would not be activated.

The data repository 12 may be able to track any RFID ID tag that is related to dangerous goods. This could be done through the adoption of a block, such as the fifth block, on any RFID tag being given a prefix code e.g.

EXPL Explosives

NACN Sodium Cyanide

H2O2 Hydrogen Peroxide

TOXC toxic chemicals

ACID acids

ALCA corrosive alkaloids

FLAM flammable materials

RADI radioactive materials

BIOH biohazards Data transfer from data collection devices 26 to the data repository is preferably sent using a protocol. For example every data transfer may be required to have: a. ID number b. Location number c. Person ID number d. Date and time e. ETC fields a. Country b. Entry type

E - Explosives manufacturer

F - Field application

G - Government bodies

M - Military R - RFID tag manufacture

S - Storage location

T - Transportation provider

The manufacturing tracking system or magazine management system may send information to an intervening computer system which will download data to the data repository 12 in batches at specified times.

Modifications and variations may be made to be present invention without departing from the basic inventive concept. Such modifications are intended to fall within the scope of the present invention the nature of which is to be determined from the foregoing description and appended claims.

Claims

1. A method of tracking at least part of the life cycle of a hazardous goods item, said method comprising: providing a data storage device arranged to store a plurality of records, each record being associated with a hazardous goods item and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item; facilitating receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices; and populating the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices.

2. A method as claimed in claim 1 , wherein the multiple distributed data gathering devices are respectively disposed at at least two of a manufacturing facility, a packaging facility, a storage facility, a transportation device, and a usage location.

3. A method as claimed in claim 1 or claim 2, wherein the life cycle data comprises data associated with a plurality of a manufacturing stage in a life cycle of an item, a packaging stage in the life cycle of an item, a transportation stage in the life cycle of an item, a storage stage in the life cycle of an item, and a usage stage in a life cycle of an item.

4. A method as claimed in any one of claims 1 to 3, comprising disposing a machine readable item tag on the hazardous goods item, the item tag including a machine readable item identifier usable to distinguish the item from other items.

5. A method as claimed in claim 4, comprising using the item identifier to associate the item with a record in the data storage device, and when the item identifier is read by an item tag reader, identifying the record associated with the item, and adding received life cycle data to the identified record.

6. A method as claimed in claim 4 or claim 5, comprising disposing a replacement item tag on an item if a previous item tag is damaged or has been inadvertently removed, and adding a replacement item identifier to the record associated with the item so as to link the new item identifier to the record associated with the previous item identifier.

7. A method as claimed in any one of claims 4 to 6, wherein the item tag comprises a RFID item tag, and at least one of the data gathering devices comprises a RFID reader.

8. A method as claimed in any one of claims 4 to 7, comprising forwarding life cycle data particular to a stage in a life cycle of an item to the data storage device when the item identifier is read at the stage.

9. A method as claimed in claim 8, wherein the life cycle data associated with a manufacturing stage comprises information indicative of the manufacturing facility, the type of item, how the item was manufactured, the components used to manufactured the item, when the item was manufactured, and/or who was involved in manufacture of the item.

10. A method as claimed in claim 8 or claim 9, wherein the life cycle data associated with a packaging stage comprises information indicative of the packaging facility, the type of package, the number of items contained in the package, how items are packaged, when items were packed, and/or who packed the items in the package.

11. A method as claimed in any one of claims 8 to 10, wherein the life cycle data associated with a storage stage comprises information indicative of the storage facility, when an item or package was transferred to the storage facility, who was involved in receiving the item or package on arrival at the storage facility, whether the item or package is returned from a usage stage, and/or who was involved in dispatching the item from the storage facility.

12. A method as claimed in any one of claims 8 to 11 , wherein the life cycle data associated with a transportation stage comprises information indicative of a transportation device, where an item or package is being taken from, where an item or package is being taken to, when the item or package was loaded onto the transportation device, when the item or package arrives at a destination, and/or who conducted the transportation.

13. A method as claimed in any one of claims 8 to 11 , wherein the life cycle data associated with a usage stage comprises information indicative of a usage location, when an item is used, and/or who used the item.

14. A method as claimed in any one of the preceding claims, comprising placing at least one item in a package and disposing a machine readable package tag on the package, the package tag including a machine readable package identifier usable to distinguish the package from other packages.

15. A method as claimed in claim 14, comprising adding a package identifier associated with a package containing an item to a record associated with the item when the package identifier is read by a package tag reader.

16. A method as claimed in claim 14 or claim 15, comprising disposing a replacement package tag on an item if a previous package tag is damaged or has been inadvertently removed, and adding a replacement package identifier to the record associated with the or each item associated with the package tag so as to link the new package identifier to the or each record associated with the previous identifier.

17. A method as claimed in any one of the preceding claims, wherein at least one of the data gathering devices comprises a data entry device usable to facilitate manual entry of life cycle data.

18. A method as claimed in any one of the preceding claims, wherein at least one of the data gathering devices comprises at least one sensor.

19. A method as claimed in any one of the preceding claims, comprising facilitating receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item through the Internet.

20. A method as claimed in any one of the preceding claims, wherein the data storage device comprises a database.

21. A method as claimed in claim 20, wherein the database is a relational database.

22. A method as claimed in any one of the preceding claims, comprising facilitating retrieval of selected data from the data storage device by a user.

23. A method as claimed in any one of the preceding claims, comprising providing different levels of access to data stored in the data storage device, and assigning one of the levels of access to each user authorised to access the data storage device.

24. A method as claimed in any one of the preceding claims, comprising securing communications to and from the data storage device.

25. A method as claimed in any one of the preceding claims, wherein the hazardous goods items comprise an explosive item, a detonator, a propellant, pyrotechnics, munitions, or a dangerous chemical/material.

26. A data repository for tracking at least part of the life cycle of a hazardous goods item, said data repository comprising: a data storage device arranged to store a plurality of records, each record being associated with a hazardous goods item and being arranged to store data indicative of at least part of the life cycle of the hazardous goods item; U2009/001308

46 the data repository being arranged to: facilitate receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices; and to populate the record associated with an item with life cycle data when life cycle data indicative of at least part of the life cycle of the item is received from any of the distributed data gathering devices.

27. A data repository as claimed in claim 1 , wherein the data repository is arranged to facilitate receipt on-line of life cycle data indicative of at least part of the life cycle of a hazardous goods item from multiple distributed data gathering devices disposed at at least two of a manufacturing facility, a packaging facility, a storage facility, a transportation device, and a usage location.

28. A data repository as claimed in claim 26 or claim 27, wherein the life cycle data comprises data associated with a plurality of a manufacturing stage in a life cycle of an item, a packaging stage in the life cycle of an item, a transportation stage in the life cycle of an item, a storage stage in the life cycle of an item, and a usage stage in a life cycle of an item.

29. A data repository as claimed in any one of claims 26 to 28, wherein each item has an associated machine readable item tag disposed on the item, each item tag has an associated unique item identifier, and each record in the data repository includes an item identifier, and when the item identifier is read by an item tag reader, the data repository is arranged to identify the record associated with the item, and to add received life cycle data to the identified record.

30. A data repository as claimed in claim 29, wherein the data repository is arranged to add a replacement item identifier to the record associated with the item so as to link the replacement item identifier to the record associated with the previous item identifier if a previous item tag is damaged or has been inadvertently removed.

31. A data repository as claimed in claim 28, wherein the life cycle data associated with a manufacturing stage comprises information indicative of the manufacturing facility, the type of item, how the item was manufactured, the components used to manufactured the item, when the item was manufactured, and/or who was involved in manufacture of the item.

32. A data repository as claimed in claim 28, wherein the life cycle data associated with a packaging stage comprises information indicative of the packaging facility, the type of package, the number of items contained in the package, how items are packaged, when items were packed, and/or who packed the items in the package.

33. A data repository as claimed in claims 28, wherein the life cycle data associated with a storage stage comprises information indicative of the storage facility, when an item or package was transferred to the storage facility, who was involved in receiving the item or package on arrival at the storage facility, whether the item or package is returned from a usage stage, and/or who was involved in dispatching the item from the storage facility.

34. A data repository as claimed in claim 28, wherein the life cycle data associated with a transportation stage comprises information indicative of a transportation device, where an item or package is being taken from, where an item or package is being taken to, when the item or package was loaded onto the transportation device, when the item or package arrives at a destination, and/or who conducted the transportation.

35. A data repository as claimed in claim 28, wherein the life cycle data associated with a usage stage comprises information indicative of a usage location, when an item is used, and/or who used the item.

36. A data repository as claimed in any one of claims 26 to 35, wherein each package containing items has an associated machine readable package tag disposed on the item, each package tag has an associated unique package identifier, and the data repository is arranged to store a package identifier in the data repository and to associate the package identifier with one or more item identifiers corresponding to the items stored in the package.

37. A data repository as claimed in any one claims 26 to 36, wherein the data repository is arranged to receive life cycle data indicative of at least part of the life cycle of a hazardous goods item through the Internet.

38. A data repository as claimed in any one claims 26 to 37, wherein the data storage device comprises a database.

39. A data repository as claimed in claim 38, wherein the database is a relational database.

40. A data repository as claimed in any one of claims 26 to 39, wherein the data repository is arranged to facilitate retrieval of selected data from the data storage device by a user.

41. A data repository as claimed in any one of claims 26 to 40, wherein the data repository is arranged to provide different levels of access to data stored in the data storage device, and to assign one of the levels of access to each user authorised to access the data storage device.

42. A data repository as claimed in any one of claims 26 to 41 , wherein the hazardous goods items comprise an explosive item, a detonator, a propellant, pyrotechnics, munitions, or a dangerous chemical/material.

43. A system for tracking at least part of the life cycle of a hazardous goods item, said system comprising: a data repository as claimed in any one of claims 26 to 42; and a plurality of distributed data gathering devices arranged to gather life cycle data indicative of at lest part of the life cycle of the item.

44. A system as claimed in claim 43, wherein the multiple distributed data gathering devices are respectively disposed at at least two of a manufacturing facility, a packaging facility, a storage facility, a transportation device, and a usage location.

45. A system as claimed in claim 43 or 44, comprising a plurality of machine readable item tags, each machine readable tag being disposed on a hazardous goods item, the item tag including a machine readable item identifier usable to distinguish the item from other items.

46. A method as claimed in claim 45, wherein the item tag comprises a RFID item tag, and at least one of the data gathering devices comprises a RFID reader.

47. A system as claimed in claim 45 or claim 46, comprising a replacement item tag, the replacement item tag being disposed on an item if a previous item tag is damaged or has been inadvertently removed, a replacement item identifier being added to the record associated with the item so as to link the new item identifier to the record associated with the previous item identifier when the replacement item tag is disposed on an item.

48. A system as claimed in any one of claims 43 to 47, comprising a plurality of machine readable package tags, each package tag being disposed on a package containing at least one item, the package tag including a machine readable package identifier usable to distinguish the package from other packages.

49. A system as claimed in claim 48, comprising a replacement package tag, the replacement package tag being disposed on an item if a previous package tag is damaged or has been inadvertently removed, a replacement package identifier to the record associated with the or each item associated with the package tag so as to link the new package identifier to the or each record associated with the previous identifier.

50. A system as claimed in any one of claims 43 to 49, wherein at least one of the data gathering devices comprises a data entry device usable to facilitate manual entry of life cycle data.

51. A method as claimed in any one of claims 43 to 50, wherein at least one of the data gathering devices comprises at least one sensor.

52. A computer program which when loaded into a computing system causes the computing system to operate in accordance with a data repository as claimed in any one of claims 26 to 42.

53. A computer readable medium having a computer program stored thereon which when loaded into a computing system causes the computing system to operate in accordance with a data repository as claimed in any one of claims 26 to 42.

54. A method of tracking an item substantially as hereinbefore described with reference to, and as shown in, the accompanying drawings.

55. A data repository for tracking an item substantially as hereinbefore described with reference to, and as shown in, the accompanying drawings.

56. A system for tracking an item substantially as hereinbefore described with reference to, and as shown in, the accompanying drawings.