Sign In to Follow Application
View All Documents & Correspondence

A System And Method For Tracking Enterprises Assest

Abstract: ABSTRACT A SYSTEM AND METHOD FOR TRACKING ENTERPRISE ASSETS The present disclosure envisages the field of asset tracking. The system for tracking enterprise assets (100) comprises a plurality of first tags (102) associated with a user, a plurality of second tags (104) associated with an enterprise asset, a scanning unit (106) and a server (108). The scanning unit (106) capture biometric of the user, decode unique user ID and unique asset ID. The server (108) generates at least one alert based on evaluation of the decoded asset ID, the decoded user ID and the biometric information received from the scanning unit (106) with the asset allocation details and the asset allocation details stored in the repository (110). The system (100) generates alerts to notify the manager and user about any invalid tracking of the asset. The system (100) enhances security of assets by preventing theft and analyzes effectively the movement of assets and employees.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
31 December 2018
Publication Number
27/2020
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
ipo@knspartners.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-12-07
Renewal Date

Applicants

ZENSAR TECHNOLOGIES LIMITED
ZENSAR KNOWLEDGE PARK, PLOT # 4, MIDC, KHARADI, OFF NAGAR ROAD, PUNE-411014, MAHARASHTRA, INDIA

Inventors

1. CHAUDHARY, Mayuresh Shantaram
D/E -128, Kadambari Nagar, Rajendra Nagar, Indore- 452012, Madhya Pradesh, India
2. AJMERA, Juhi Dineshchandra
255, Chanakya Puri, Hiran Magri, Secotr-4, Udaipur-313002, Rajasthan, India
3. PARAKH, Nilesh Prakash
M-5, Kumar Park View Cooperative Housing Society, Bibwewadi- Kondhwa Road, Kenjale Nagar, Bibwewadi, Pune-411037, Maharashtra, India
4. BADJATYA, Paridhi Jitendra
178 Sukhdev Nagar, Extension 2, Aerodrome Road, Indore-452005, Madhya Pradesh, India
5. SAMDARE, Vikram
A-28, Mount N Glory, Kharadi, Pune-411014, Maharashtra, India

Specification

DESC:FIELD
The present invention relates to the field of asset tracking.
DEFINITION
As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used indicate otherwise.

The term ‘asset’ provided in this disclosure refers to owned and rented assets like buildings, furniture, LED TVs, projectors, laptops, electric devices, mobiles and the like etc. Many employees are assigned assets such as laptops, mobiles and other devices that need to be tagged to the employees and tracked for their current handlers and whereabouts.
BACKGROUND
The background information herein below relates to the present disclosure but is not necessarily prior art.
Generally, in any industry, tracking of assets allocation and movement is being done by maintaining data in excel sheets that need manual handling. The tracking is done by physically going to the locations where the assets are placed and noting the asset numbers or barcode numbers assigned to the assets. The information is then compiled to prepare various reports. This process makes asset tracking a tedious work and there is a high chance of leaving some assets such as laptops assigned to employees untraceable for long time. Employee using assets allocated to other employees is also one of the issues that lead to theft and wrong asset allocations. This is an unethical practice that causes the asset theft or not returned to the company.
In addition, the asset tracking such as current location and employee possession is not visible on day to day basis. This creates difficulty for logistics department in accurately identifying whether the asset is moving in and out in some location by expected employee on regular basis or its being used by other employees who are not assigned the asset.
There is, therefore, felt a need for providing a system and method for tracking enterprise assets.
OBJECTS
Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:
An object of the present disclosure is to provide a system and method for tracking enterprise assets.
Another object of the present disclosure is to provide a system to enhance security of assets by preventing theft.
Yet another object of the present disclosure is to provide a system that improves the chances of theft prevention using just-in time alert system.

Still another object of the present disclosure is to provide a system that analyzes effectively the movement of assets and employees.

Another object of the present disclosure is to provide a system to provide intelligent programming with strategically located readers which also can help in tracking movement of various assets and employees within the premises in real-time.

Yet another object of the present disclosure is to provide a system that tracks multiple assets assigned to one employee.

Still another object of the present disclosure is to provide a system that verifies and marks attendance for the employees for the day.
Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
SUMMARY
The present disclosure envisages a system and method for tracking enterprise assets
The system for tracking enterprise assets a plurality of first tags, a plurality of second tags, a scanning unit and a server.
Each of the first tag is associated with a user and contains a unique user ID of the user.
Each of the second tag is associated with an enterprise asset and contain a unique asset ID.
The scanning unit configured to scan the first tag and the second tag, and further configured to capture at least one biometric information of the user carrying the enterprise asset. The scanning unit configured to decode the unique user ID and the unique asset ID from the scanned first tag and the scanned second tag respectively.
The scanning unit includes a scanner, a decoder and a biometric processing unit.
The scanner configured to scan the first tag and the second tag and further configured to generate a first scanned information corresponding to the scanned first tag and a second scanned information corresponding to the scanned second tag.
The decoder configured to cooperate with the scanner, and further configured to decode the first scanned information and the second scanned information to generate the decoded unique user ID and the decoded unique asset ID respectively.
The biometric processing unit configured to capture and process the biometric information of the user on passing through a scanning area, and further configured to generate a processed biometric information.
The scanner, decoder and biometric processing unit are implemented using one or more processor(s).
The server is communicatively coupled with the scanning unit. The server comprises a repository and an evaluator.
The repository configured to store asset allocation details wherein the asset allocation details include a list of allotted asset IDs, user ID of the user corresponding to each of the allotted asset IDs, and biometric information of the users corresponding to each of the allotted asset IDs.
The evaluator configured to cooperate with the repository, the evaluator configured to evaluate the decoded asset ID, the decoded user ID and the biometric information with the asset allocation details to track the enterprise asset, and generate at least on alert based on the evaluation.
The evaluator includes a first crawler and extractor, a second crawler and extractor, a flag generator, and an alert generator.
The first crawler and extractor configured to cooperate with the scanning unit and the repository, and further configured to crawl through the asset allocation details to extract the unique user ID corresponding to the decoded asset ID.
The second crawler and extractor configured to cooperate with the repository and the scanning unit, and further configured to crawl through the asset allocation details to extract the biometric information corresponding to the decoded asset ID.
The flag generator configured to cooperate with the first crawler and extractor and the second crawler and extractor, and further configured to
o generate a first flag when the extracted unique ID is not equal to the decoded user ID; and
o generate a second flag when the extracted biometric information is not equal to the processed biometric information.

The alert generator configured to cooperate with the flag generator, and further configured to generate a first alert on generation of at least one of the flag.

The first crawler and extractor, second crawler and extractor, flag generator and alert generator are implemented using one or more processor(s).

The evaluator further comprises a tracking unit configured to store log details pertaining to the scanned user ID and the scanned biometric ID corresponding to the asset ID.

The log details are provided to senior management and the user allotted the enterprise asset.

A second alert is generated on detection of a damaged first tag or a second tag, and a third alert is generated on unsuccessful scanning of the first tag or the second tag.

In an embodiment, the biometric information is selected from the group consisting of, but not limited to, fingerprint, palm veins, face recognition, palm print, hand geometry, iris recognition, retina and voice recognition.

The present disclosure envisages a method for tracking enterprise assets. The steps include:
• associating, a plurality of first tags, wherein each of the first tag is associated with a user and contain a unique user ID of the user;
• associating, a plurality of second tags, wherein each of the second tag is associated with an asset and contain a unique asset ID;
• scanning, by a scanning unit, the first tag and the second tag;
• capturing, by the scanning unit, at least one biometric information of the user carrying the enterprise asset;
• decoding, by the scanning unit, the unique user ID and the unique asset ID from the scanned first tag and the scanned second tag, respectively;
• storing, by a repository, asset allocation details wherein the asset allocation details include a list of allotted asset IDs, user ID of the user corresponding to each of the allotted asset ID, and biometric information of the users carrying the enterprise asset corresponding to each of the asset ID;
• evaluating, by an evaluator, the decoded asset ID, the decoded user ID and the biometric information with the asset allocation details to track the enterprise asset; and
• generating, by the evaluator, at least one alert based on the evaluation.

The step of evaluating the decoded asset ID, the decoded user ID and the biometric information with the asset allocation details to track the enterprise asset includes the sub-steps of:
• crawling, by a first crawler and extractor, through asset allocation details wherein the asset allocation details include a list of allotted asset IDs, user ID of the user corresponding to each of the allotted asset IDs, and biometric information of the users corresponding to each of the allotted asset IDs and extracting, by the first crawler and extractor, the unique user ID corresponding to the decoded asset ID;
• crawling, by a second crawler and extractor, through the asset allocation details and extracting, by the second crawler and extractor (120), the biometric information corresponding to the decoded asset ID;
• generating, by a flag generator, a first flag when the extracted unique ID is not equal to the decoded user ID; and
• generating, by the flag generator, a second flag when the extracted biometric information is not equal to the processed biometric information.
The step of generating at least one alert based on the evaluation includes the sub-steps of:
• detecting, by an alert generator, status of the first flag;
• generating, by the alert generator, a first alert based on the status of the first flag;
• detecting, by the alert generator, status of the second flag; and
generating, by the alert generator, a second alert based on the status of the second flag.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
A system and method for tracking enterprise assets of the present disclosure will now be described with the help of the accompanying drawing, in which:
Figure 1 illustrates a block diagram for tracking enterprise assets; and
Figure 2a and 2b illustrate a flow diagram of a method for tracking enterprise assets.
LIST OF REFERENCE NUMERALS
100 System
102 first tags
104 second tags
106 scanning unit
108 server
110 repository
112 evaluator
114 scanner
116 decoder
118 biometric processing unit
120 first crawler and extractor
122 second crawler and extractor
124 flag generator
126 tracking unit
DETAILED DESCRIPTION
Embodiments, of the present disclosure, will now be described with reference to the accompanying drawing.
Embodiments are provided so as to thoroughly and fully convey the scope of the present disclosure to the person skilled in the art. Numerous details, are set forth, relating to specific components, and methods, to provide a complete understanding of embodiments of the present disclosure. It will be apparent to the person skilled in the art that the details provided in the embodiments should not be construed to limit the scope of the present disclosure. In some embodiments, well-known processes, well-known apparatus structures, and well-known techniques are not described in detail.
The terminology used, in the present disclosure, is only for the purpose of explaining a particular embodiment and such terminology shall not be considered to limit the scope of the present disclosure. As used in the present disclosure, the forms "a,” "an," and "the" may be intended to include the plural forms as well, unless the context clearly suggests otherwise. The terms "comprises," "comprising," “including,” and “having,” are open ended transitional phrases and therefore specify the presence of stated features, elements, modules, units and/or components, but do not forbid the presence or addition of one or more other features, elements, components, and/or groups thereof.
A system and method for tracking enterprise assets of the present disclosure, is described with reference to Figure 1 through Figure 2b.
Referring to Figure 1, the system for tracking enterprise assets (hereinafter referred as “system”) (100) comprises a plurality of first tags (102), a plurality of second tags (104), a scanning unit (106) and a server (108).
Each of the first tag (102) is associated with a user and contains a unique user ID of the user.
Each of the second tag (104) is associated with an enterprise asset and contain a unique asset ID.
The scanning unit (106) configured to scan the first tag (102) and the second tag (104), and further configured to capture at least one biometric information of the user carrying the enterprise asset. The scanning unit (106) configured to decode the unique user ID and the unique asset ID from the scanned first tag (102) and the scanned second tag (104) respectively.
The scanning unit (106) includes a scanner (114), a decoder (116) and a biometric processing unit (118).
The scanner (114) configured to scan the first tag (102) and the second tag (104), and further configured to generate a first scanned information corresponding to the scanned first tag (102) and a second scanned information corresponding to the scanned second tag (104).
An exemplified pseudocode for the scanner (114) is given below:
Program (scanner)
Read tags,
Do
{
scan the first tag (102) and the second tag (104); and
generate a first scanned information corresponding to the scanned first tag (102) and a second scanned information corresponding to the scanned second tag (104).
} While (Read tags)
End
The decoder (116) configured to cooperate with the scanner (114), and further configured to decode the first scanned information and the second scanned information to generate the decoded unique user ID and the decoded unique asset ID respectively.
An exemplified pseudocode for the decoder (116) is given below:
Program (decoder)
Read first scanned information and second scanned information,
Do
{
decode the first scanned information and the second scanned information; and
generate the decoded unique user ID and the decoded unique asset ID respectively.
} While (Read first scanned information and second scanned information)
End
The biometric processing unit (118) configured to capture and process the biometric information of the user on passing through a scanning area, and further configured to generate a processed biometric information.
An exemplified pseudocode for the biometric processing unit (118) is given below:
Program (biometric processing)
Read biometric,
Do
{
capture and process the biometric information of the user on passing through a scanning area; and
generate a processed biometric information.
} While (Read biometric)
End
The scanner (114), decoder (116) and biometric processing unit (118) are implemented using one or more processor(s).
The server (108) is communicatively coupled with the scanning unit (106). The server (108) comprises a repository (110) and an evaluator (112).
The repository (110) configured to store asset allocation details wherein the asset allocation details include a list of allotted asset IDs, user ID of the user corresponding to each of the allotted asset IDs, and biometric information of the users corresponding to each of the allotted asset IDs.
The evaluator (112) configured to cooperate with the repository (110), the evaluator (112) configured to evaluate the decoded asset ID, the decoded user ID and the biometric information with the asset allocation details to track the enterprise asset, and generate at least on alert based on the evaluation.
The evaluator (112) includes a first crawler and extractor (120), a second crawler and extractor (122), a flag generator (124), and an alert generator (126).
The first crawler and extractor (120) configured to cooperate with the scanning unit (106) and the repository (110), and further configured to crawl through the asset allocation details to extract the unique user ID corresponding to the decoded asset ID.
An exemplified pseudocode for the first crawler and extractor (120) is given below:
Program (first crawler and extractor)
Read decoded asset ID,
Do
{
crawl through the asset allocation details to extract the unique user ID corresponding to the decoded asset ID.
} While (Read decoded asset ID)
End
The second crawler and extractor (122) configured to cooperate with the repository (110) and the scanning unit (106), and further configured to crawl through the asset allocation details to extract the biometric information corresponding to the decoded asset ID.
An exemplified pseudocode for the second crawler and extractor (122) is given below:
Program (second crawler and extractor)
Read decoded asset ID,
Do
{
crawl through the asset allocation details to extract the biometric information corresponding to the decoded asset ID.
} While (Read decoded asset ID)
End
The flag generator (124) configured to cooperate with the first crawler and extractor (120) and the second crawler and extractor (122), and further configured to
o generate a first flag when the extracted unique ID is not equal to the decoded user ID; and
o generate a second flag when the extracted biometric information is not equal to the processed biometric information.
An exemplified pseudocode for the flag generator (124) is given below:
Program (flag generator)
Read extracted unique ID, decoded user ID, extracted biometric information, processed biometric information
Do
{
generate a first flag when the extracted unique ID is not equal
to the decoded user ID; and
generate a second flag when the extracted biometric
information is not equal to the processed biometric information
} While (Read extracted unique ID, decoded user ID, extracted biometric information, processed biometric information)
End
The alert generator (126) configured to cooperate with the flag generator (124), and further configured to generate a first alert on generation of at least one of the flag.
An exemplified pseudocode for the alert generator (126) is given below:
Program (alert generator)
Read flags,
Do
{
generate a first alert on generation of at least one of the flag
} While (Read flags)
End

The first crawler and extractor (120), second crawler and extractor (122), flag generator (124) and alert generator (126) are implemented using one or more processor(s).
The processor may be a general-purpose processor, a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), and/or the like. The processor may be configured to retrieve data from and/or write data to the memory. The memory can be for example, a random access memory (RAM), a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a read only memory (ROM), a flash memory, a hard disk, a floppy disk, cloud storage, and/or so forth.
The evaluator (112) further comprises a tracking unit (128) configured to store log details pertaining to the scanned user ID and the scanned biometric ID corresponding to the asset ID.
An exemplified pseudocode for the tracking unit (128) is given below:
Program (tracking)
Read scanned user ID and the scanned biometric ID corresponding to the asset ID,
Do
{
store log details pertaining to the scanned user ID and the scanned biometric ID corresponding to the asset ID.
} While (Read scanned user ID and the scanned biometric ID corresponding to the asset ID)
End
The log details are provided to senior management and the user allotted the enterprise asset. In an another embodiment, the log details are stored for averting future mishaps.
In another embodiment, the log details are displayed on screen (not shown in the figures) to be verified by the security staff.
A second alert is generated on detection of a damaged first tag (102) or a second tag (104), and a third alert is generated on unsuccessful scanning of the first tag (102) or the second tag (104).
In an embodiment, the biometric information is selected from the group consisting of, but not limited to, fingerprint, palm veins, face recognition, palm print, hand geometry, iris recognition, retina and voice recognition.
In an operative embodiment, the system (100) implements a two-layer verification, i.e., verifying user ID extracted from first tag (102) and biometric verification. The first tag (102) contains a unique user ID and is associated with the user. The second tag (104) contains a unique asset ID and is associated with an enterprise asset. The user passes the scanning area. The first tag (102) and the second tag (104) are scanned by a scanning unit (106) and at least one biometric information of the user carrying the enterprise asset is captured, for example face, retina, fingerprint etc. The scanning unit (106) decodes the unique user ID and the unique asset ID from the scanned first tag (102) and the scanned second tag (104) respectively. The evaluator (112) evaluate the decoded asset ID, the decoded user ID and the biometric information with the asset allocation details stored in the repository (110) to track the enterprise asset.
The system (100) generates at least on alert based on the evaluation. For example: in case when the asset ID does not match the user ID, a flag is generated. In another case if the biometric information of the allotted user carrying the asset is not same as that of processed biometric information, another flag is generated. Also, when the tags are not scanned properly and on an event when the tags are damaged, an alert is generated.
The log details pertaining to the scanned user ID and the scanned biometric ID corresponding to the asset ID are stored by the system (100) and provided to senior management and the user allotted the enterprise asset.
The cases are explained below:
Case 1:
The user, accompanied with the first tag (102), passes through the scanning area along with an asset having the second tag (104). The scanning unit (106) scans the first tag (102), second tag (104) and the biometric information of the user. If the asset is carried by the user allotted, no flag is generated.
Case 2:
If the allotted user ID is not same as that of decoded user ID, a flag is generated. Further, if the biometric information of the allotted user is not same as that of processed biometric information, another flag is generated. In an event when either of the flag is generated, an alert is generated.
Case 3:
If the first tag (102) or the second tag (104) are not scanned properly, a second alert is generated.
Case 4:
If the first tag (102) or the second tag (104) are damaged, a third alert is generated.
In a working embodiment, image of the user’s face is captured as the biometric information. At least one image is captured by the scanning unit (106) for the facial recognition. The captured image is first enhanced and converted into a grayscale image. The grayscale image is processed to determine a region of interest (ROI) within the greyscale image. The determined ROI within the greyscale image is segmented into at least two regions. The pixel values of these two regions are compared with the facial parameters of the user which are pre-stored in the repository (110) as biometric information.
In an embodiment, the first tag (102) and the second tag (104) is selected from the group consisting of, but not limited to, RFID tags.
RFID is quick-fit, highly customizable, scalable, robust and provides low-latency support time in all kinds of theft detection and prevention scenario.
In another embodiment, the first tag (102) and the second tag (104) used are custom designed. They can be changed based on the application.
In another embodiment, different reports are generated like rule violation reports and alerts dispatcher reports.
Figures 2a and 2b illustrate a flow diagram of a method for tracking enterprise assets. The steps include:
• Step 202: associating (202), a plurality of first tags (102), wherein each of the first tag (102) is associated with a user and contain a unique user ID of the user;
• Step 204: associating (204), a plurality of second tags (104), wherein each of the second tag (104) is associated with an asset and contain a unique asset ID;
• Step 206: scanning (206), by a scanning unit (106), the first tag (102) and the second tag (104);
• Step 208: capturing (208), by the scanning unit (106), at least one biometric information of the user carrying the enterprise asset;
• Step 210: decoding (210), by the scanning unit (106), the unique user ID and the unique asset ID from the scanned first tag (102) and the scanned second tag (104), respectively;
• Step 212: storing (212), by a repository (110), asset allocation details wherein the asset allocation details include a list of allotted asset IDs, user ID of the user corresponding to each of the allotted asset ID, and biometric information of the users carrying the enterprise asset corresponding to each of the asset ID;
• Step 214: evaluating (214), by an evaluator (112), the decoded asset ID, the decoded user ID and the biometric information with the asset allocation details to track the enterprise asset; and
• Step 216: generating (216), by the evaluator (112), at least one alert based on the evaluation.
The step of evaluating the decoded asset ID, the decoded user ID and the biometric information with the asset allocation details to track the enterprise asset includes the sub-steps of:
• crawling, by a first crawler and extractor (120), through asset allocation details wherein the asset allocation details include a list of allotted asset IDs, user ID of the user corresponding to each of the allotted asset IDs, and biometric information of the users corresponding to each of the allotted asset IDs and extracting, by the first crawler and extractor (120), the unique user ID corresponding to the decoded asset ID;
• crawling, by a second crawler and extractor (120), through the asset allocation details and extracting, by the second crawler and extractor (120), the biometric information corresponding to the decoded asset ID;
• generating, by a flag generator (124), a first flag when the extracted unique ID is not equal to the decoded user ID; and
• generating, by the flag generator (124), a second flag when the extracted biometric information is not equal to the processed biometric information.
The step of generating at least one alert based on the evaluation includes the sub-steps of:
• detecting, by an alert generator (126), status of the first flag;
• generating, by the alert generator (126), a first alert based on the status of the first flag;
• detecting, by the alert generator (126), status of the second flag; and
• generating, by the alert generator (126), a second alert based on the status of the second flag.

TECHNICAL ADVANCEMENTS
The present disclosure described herein above has several technical advantages including, but not limited to, the realization of, a system and method for tracking enterprise assets, which:
• enhance security of assets by preventing theft;
• improves the chances of theft prevention using just-in time alert system;
• analyzes effectively the movement of assets and employees;
• provide intelligent programming with strategically located readers which also can help in tracking movement of various assets and employees within the premises in real-time;
• tracks multiple assets assigned to one user; and
• verifies and marks attendance for the employees for the day.
The foregoing disclosure has been described with reference to the accompanying embodiments which do not limit the scope and ambit of the disclosure. The description provided is purely by way of example and illustration.
The embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
The foregoing description of the specific embodiments so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
Throughout this specification the word “comprise”, or variations such as “comprises” or “comprising”, will be understood to imply the inclusion of a stated element, step, or group of elements, steps, but not the exclusion of any other element, or step, or group of elements, or steps.
The use of the expression “at least” or “at least one” suggests the use of one or more elements or ingredients or quantities, as the use may be in the embodiment of the disclosure to achieve one or more of the desired objects or results.
While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
,CLAIMS:WE CLAIM:
1. A system (100) for tracking enterprise assets, said system (100) comprising:
• a plurality of first tags (102), wherein each of said first tag (102) is associated with a user and contains a unique user ID of said user;
• a plurality of second tags (104), wherein each of said second tag (104) is associated with an enterprise asset and contain a unique asset ID;
• a scanning unit (106) configured to scan said first tag (102) and said second tag (104), and further configured to capture at least one biometric information of said user carrying said enterprise asset, said scanning unit (106) configured to decode said unique user ID and said unique asset ID from said scanned first tag (102) and said scanned second tag (104) respectively;
• a server (108) communicatively coupled with said scanning unit (106), said server (108) comprising:
o a repository (110) configured to store asset allocation details wherein said asset allocation details include a list of allotted asset IDs, user ID of said user corresponding to each of said allotted asset IDs, and biometric information of said users corresponding to each of said allotted asset IDs; and
o an evaluator (112) configured to cooperate with said repository (110), said evaluator (112) configured to evaluate said decoded asset ID, said decoded user ID and said biometric information with said asset allocation details to track said enterprise asset, and generate at least on alert based on said evaluation.
2. The system (100) as claimed in claim 1, wherein said scanning unit (106) includes:
• a scanner (114) configured to scan said first tag (102) and said second tag (104), and further configured to generate a first scanned information corresponding to said scanned first tag (102) and a second scanned information corresponding to said scanned second tag (104);
• a decoder (116) configured to cooperate with said scanner (114), and further configured to decode said first scanned information and said second scanned information to generate said decoded unique user ID and said decoded unique asset ID respectively; and
• a biometric processing unit (118) configured to capture and process said biometric information of said user on passing through a scanning area, and further configured to generate a processed biometric information,
wherein said scanner (114), said decoder (116), said biometric processing unit (118) are implemented using one or more processor(s).
3. The system (100) as claimed in claim 1, wherein said evaluator (112) includes:
• a first crawler and extractor (120) configured to cooperate with said scanning unit (106) and said repository (110), and further configured to crawl through said asset allocation details to extract said unique user ID corresponding to said decoded asset ID;
• a second crawler and extractor (122) configured to cooperate with said repository (110) and said scanning unit (106), and further configured to crawl through said asset allocation details to extract said biometric information corresponding to said decoded asset ID; and
• a flag generator (124) configured to cooperate with said first crawler and extractor (120) and said second crawler and extractor (122), and further configured to
o generate a first flag when said extracted unique ID is not equal to said decoded user ID; and
o generate a second flag when said extracted biometric information is not equal to said processed biometric information,
• an alert generator (126) configured to cooperate with said flag generator (124), and further configured to generate a first alert on generation of at least one of said flags,
wherein said first crawler and extractor (120), said second crawler and extractor (122), said flag generator (124) and said alert generator (126) are implemented using one or more processor(s).
4. The system (100) as claimed in claim 1, wherein said evaluator (112) further comprises a tracking unit (128) configured to store log details pertaining to said scanned user ID and said scanned biometric ID corresponding to said asset ID.
5. The system (100) as claimed in claim 4, wherein said log details are provided to senior management and said user allotted said enterprise asset.
6. The system (100) as claimed in claim 1, wherein a second alert is generated on detection of a damaged first tag (102) or a second tag (104), and a third alert is generated on unsuccessful scanning of said first tag (102) or said second tag (104).
7. The system (100) as claimed in claim 1, wherein said biometric information is selected from the group consisting of fingerprint, palm veins, face recognition, palm print, hand geometry, iris recognition, retina and voice recognition.
8. A method for tracking enterprise assets, said method comprising following steps:
• associating (202), a plurality of first tags (102), wherein each of said first tag (102) is associated with a user and contain a unique user ID of said user;
• associating (204), a plurality of second tags (104), wherein each of said second tag (104) is associated with an asset and contain a unique asset ID;
• scanning (206), by a scanning unit (106), said first tag (102) and said second tag (104);
• capturing (208), by said scanning unit (106), at least one biometric information of said user carrying said enterprise asset;
• decoding (210), by said scanning unit (106), said unique user ID and said unique asset ID from said scanned first tag (102) and said scanned second tag (104), respectively;
• storing (212), by a repository (110), asset allocation details wherein said asset allocation details include a list of allotted asset IDs, user ID of said user corresponding to each of said allotted asset ID, and biometric information of said users carrying said enterprise asset corresponding to each of said asset ID;
• evaluating (214), by an evaluator (112), said decoded asset ID, said decoded user ID and said biometric information with said asset allocation details to track said enterprise asset; and
• generating (216), by the evaluator (112), at least one alert based on said evaluation.
9. The method as claimed in claim 8, wherein the step of evaluating said decoded asset ID, said decoded user ID and said biometric information with said asset allocation details to track said enterprise asset includes the sub-steps of:
• crawling, by a first crawler and extractor (120), through asset allocation details wherein said asset allocation details include a list of allotted asset IDs, user ID of said user corresponding to each of said allotted asset IDs, and biometric information of said users corresponding to each of said allotted asset IDs and extracting, by said first crawler and extractor (120), said unique user ID corresponding to said decoded asset ID;
• crawling, by a second crawler and extractor (120), through said asset allocation details and extracting, by said second crawler and extractor (120), said biometric information corresponding to said decoded asset ID;
• generating, by a flag generator (124), a first flag when said extracted unique ID is not equal to said decoded user ID; and
• generating, by said flag generator (124), a second flag when said extracted biometric information is not equal to said processed biometric information.
10. The method as claimed in claim 8, wherein the step of generating at least one alert based on said evaluation includes the sub-steps of:
• detecting, by an alert generator (126), status of said first flag;
• generating, by said alert generator (126), a first alert based on said status of said first flag;
• detecting, by said alert generator (126), status of said second flag; and
• generating, by said alert generator (126), a second alert based on said status of said second flag.

Documents

Application Documents

# Name Date
1 201821049984-STATEMENT OF UNDERTAKING (FORM 3) [31-12-2018(online)].pdf 2018-12-31
2 201821049984-PROVISIONAL SPECIFICATION [31-12-2018(online)].pdf 2018-12-31
3 201821049984-PROOF OF RIGHT [31-12-2018(online)].pdf 2018-12-31
4 201821049984-POWER OF AUTHORITY [31-12-2018(online)].pdf 2018-12-31
5 201821049984-FORM 1 [31-12-2018(online)].pdf 2018-12-31
6 201821049984-DRAWINGS [31-12-2018(online)].pdf 2018-12-31
7 201821049984-DECLARATION OF INVENTORSHIP (FORM 5) [31-12-2018(online)].pdf 2018-12-31
8 201821049984-Proof of Right (MANDATORY) [07-05-2019(online)].pdf 2019-05-07
9 201821049984-ENDORSEMENT BY INVENTORS [06-08-2019(online)].pdf 2019-08-06
10 201821049984-DRAWING [06-08-2019(online)].pdf 2019-08-06
11 201821049984-COMPLETE SPECIFICATION [06-08-2019(online)].pdf 2019-08-06
12 Abstract1.jpg 2019-09-14
13 201821049984-FORM 18 [25-10-2019(online)].pdf 2019-10-25
14 201821049984-ORIGINAL UR 6(1A) FORM 1-080519.pdf 2019-12-31
15 201821049984-RELEVANT DOCUMENTS [29-09-2021(online)].pdf 2021-09-29
16 201821049984-FORM-26 [29-09-2021(online)].pdf 2021-09-29
17 201821049984-FORM 13 [29-09-2021(online)].pdf 2021-09-29
18 201821049984-OTHERS [06-10-2021(online)].pdf 2021-10-06
19 201821049984-FER_SER_REPLY [06-10-2021(online)].pdf 2021-10-06
20 201821049984-COMPLETE SPECIFICATION [06-10-2021(online)].pdf 2021-10-06
21 201821049984-CLAIMS [06-10-2021(online)].pdf 2021-10-06
22 201821049984-FER.pdf 2021-10-18
23 201821049984-PatentCertificate07-12-2023.pdf 2023-12-07
24 201821049984-IntimationOfGrant07-12-2023.pdf 2023-12-07

Search Strategy

1 201821049984_searchE_30-03-2021.pdf

ERegister / Renewals

3rd: 20 Feb 2024

From 31/12/2020 - To 31/12/2021

4th: 20 Feb 2024

From 31/12/2021 - To 31/12/2022

5th: 20 Feb 2024

From 31/12/2022 - To 31/12/2023

6th: 20 Feb 2024

From 31/12/2023 - To 31/12/2024

7th: 07 Nov 2024

From 31/12/2024 - To 31/12/2025

8th: 06 Oct 2025

From 31/12/2025 - To 31/12/2026