gement systems allow network administrators to track company assets and provide them with information such as asset manufacturer, installed applications, inventory ID and services provided. Typically, asset management sys- tems assist administrators in purchasing new equipment, detecting computing resources and allocating maintenance/asset cost for each group or division of the organisation. Commercial asset management systems provide few facilities for automatically locating assets and keeping track of their movements. Operators are responsible for updating the information in the asset database concerning asset location whenever assets change position. Owing to this half-automatic asset management procedure, the asset database frequently has a random mixture of fresh and outdated location information. Computer-based telephony applications are slowly substituting conventional telephony equipment. The basic idea is that each mobile user has a computer to which incoming calls are diverted. Network servers are responsible for transparently diverting calls to the position of the mobile host. Hence it is increasingly important that tools are available to keep track of the physical host position in order to: Locate malfunctioning computers that are connected to a large network. Allow some applications such as computer-based telephony applications to function. Find how to contact the user of a mobile computer that is malfunctioning at any given moment. For instance, an asset tracking system should provide the number of the telephone that is closest to such a user. An effective asset localisation system would be a prime example of software that has high ROI and good connectivity. The SNMP community attempted to address the problem of asset localisation by specifying the sysLocation variable in MIB-II. The variable sysLocation contains the location of the asset in a unspecified form such as building, floor and room. In order to use this solution: An SNMP agent must run on each asset. In order to retrieve asset positions, 