Patent ID: 12236698

DETAILED DESCRIPTION OF THE INVENTION

The systems and methods disclosed herein are described in detail by way of examples and with reference to the figures. It will be appreciated that modifications to disclosed and described examples, arrangements, configurations, components, elements, apparatuses, devices methods, systems, etc. can suitably be made and may be desired for a specific application. In this disclosure, any identification of specific techniques, arrangements, etc. are either related to a specific example presented or are merely a general description of such a technique, arrangement, etc. Identifications of specific details or examples are not intended to be, and should not be, construed as mandatory or limiting unless specifically designated as such.

Office machines, such as MFPs, are frequently managed and maintained as a fleet, frequently by third party service providers. When a site is assessed for device management, it is typically done with an onsite visit. In an example scenario, a two person team comprised of a company information technology technician and a distributor employee are dispatched to a site. The team must travel to the facility. They then complete a premises walk through to identify, catalog and mark each device with an identification tag. This can involve hours of costly human resource time. Example embodiments herein provide an asset management system that deploys templates to individual devices for automated tagging and registration of devices with minimal time requirements, minimal costs and improved accuracy.

FIG.1illustrates an example embodiment of a system100for remote asset tagging and management. Included are one or more MFPs, such as MFPs104,108,112and118. In the illustrated example, the MFPs are dispersed at a single location, but it is to be understood that they may be deployed in multiple locations. MFP locations are suitably determined in accordance with any suitable positioning system, including positions established by an IP address, geolocation such as with GPS satellites116, one or more Wi-Fi hotspots, such as Wi-Fi hotspot120, or one or more cell towers, such as cell tower124. The MFPs are in data communication with server128via network cloud,132comprised of any suitable wireless or wired data network. Network cloud132is suitably comprised of a local area network (LAN), a wide area network (WAN), which may comprise the Internet, or any suitably combination thereof. Server128identifies candidate devices by any suitable means, such as by checking devices in a particular subnet. Once candidate devices are determined, a template, such as template136, is disposed for printing or display at each device. Included in template136is an encoded indicia, such as QR code140. A user, such as user144, scans the QR code with their tablet, smartphone, such as smartphone148, or by using the MFP itself. This results in automated cataloging of the associated device and printing of an asset tag, such as asset tag142, which can be affixed to the associated device. Details on generating templates and asset tags, as well as device cataloging, are provided further below. While QR codes are used in examples herein, it is to be understood that any suitable encoded indicia, including barcodes, or readable character indicia is suitably used.

Turning now toFIG.2, illustrated is an example embodiment of a networked digital device comprised of document rendering system200suitably comprised within an MFP, such as with MFPs104,108,112and116ofFIG.1. It will be appreciated that an MFP includes an intelligent controller204which is itself a computer system. Thus, an MFP can itself function as a server with the capabilities described herein. Included in intelligent controller204are one or more processors, such as that illustrated by processor (CPU)208. Each processor is suitably associated with non-volatile memory, such as read-only memory (ROM)212, and random access memory (RAM)216, via a data bus220.

Processor208is also in data communication with input/output interface222, suitably comprising a user touchscreen. While touchscreens are discussed in example embodiments herein, it is to be appreciated that any suitable user interface, such as keyboards, switches, displays, trackballs or mice may be used.

Processor208is also in data communication with a storage interface224for reading or writing to a storage228, suitably comprised of a hard disk, optical disk, solid-state disk, cloud-based storage, or any other suitable data storage as will be appreciated by one of ordinary skill in the art.

Processor208is also in data communication with additional interfaces, such as Bluetooth interface226, NFC interface230and card reader232for data exchange with proximity cards, such as card keys.

Processor208is also in data communication with a network interface236which provides an interface to a network interface controller (NIC)240, which in turn provides a data path to any suitable wired interface or physical network connection244, or to a wireless data connection via wireless network interface248. Example wireless data connections include cellular, Wi-Fi, wireless universal serial bus (wireless USB), satellite, and the like. Example wired interfaces include Ethernet, USB, IEEE 1394 (FireWire), Lightning, telephone line, or the like.

Processor208can also be in data communication with any suitable user input/output (I/O) network interface248which provides data communication for interfacing with user peripherals, such as displays, keyboards, mice, track balls, touch screens, or the like. Processor208can also be in communication with hardware monitor252, such as a page counter, temperature sensor, toner or ink level sensor, paper level sensor, or the like.

Also in data communication with data bus220is a document processor interface256suitable for data communication with the document rendering system260, including MFP functional units. In the illustrated example, these units include a scan engine comprising copy hardware264, a scan engine comprise of scan hardware268, a print engine comprised of print hardware272and a fax engine comprised of fax hardware276which together comprise MFP document rendering system260. It will be understood that functional units are suitably comprised of intelligent units, including any suitable hardware or software platform.

Turning now toFIG.3, illustrated is an example embodiment of a digital data processing device300such as server128or smartphone148ofFIG.1. It is to be appreciated that some components listed may be unnecessary in certain configurations. Components of the digital data processing device300suitably include one or more processors, illustrated by processor304, memory, suitably comprised of read-only memory308and random access memory312, and bulk or other non-volatile storage316, suitably connected via a storage interface320. Data communication among components is accomplished via data bus324. A network interface controller328suitably provides a gateway for data communication with other devices, via any wireless or wired connection, such as via wireless network interface332. A user input/output interface336is suitably comprised of display generator340interfacing with touchscreen display344. As noted above, any suitable user input and display can be used. User input/output interface336also provides connection to biometric sensor348, suitably comprised of a fingerprint sensor, retinal sensor, or the like, and may be used to secure device access to one or more users. Processor304is also in data communication with a digital camera352, suitably used to capture images which may include encoded images such as barcodes or QR codes. Digital camera352is also suitably used for facial recognition, including facial recognition for securing device access.

FIG.4illustrates a flowchart400of an example embodiment of a system for remote asset tagging and management, suitably run in conjunction with server128ofFIG.1. The process commences at block404and proceeds to block408where a subnet is identified. Once a subnet has been identified, a search is made at block412for candidate devices in that subnet. A test is made at block416to determine if one or more candidate devices have been found. If not, the process ends at block420.

When one or more devices have been found at block416, a first device is selected and its model number and/or serial number is pulled from the device at block424. A test is made at block428to determine if the device already exists in a database. If not, it is added to the database at block432and a check is made at block440to determine if an associate asset ID exists in the record. If not, one is added at block444. Next, a determination is made at block448as to whether a service number exists in the record. If not, one is added at block452. Next, the asset ID and service number is sent to the device at block436which then prints a tag sheet with a QR code and device tag on the MFP at block456. A test is made at block460to determine whether the QR code has been scanned with a smartphone. If so, location data is obtained from the smartphone at block464. If a smartphone was not used for scanning the QR code, the process proceeds to block468to determine whether it was scanned by the MFP. If not, the process ends at block472. Location information from a smartphone scan or an MFP scan is added to the database record at block476, and the device is registered at block480. A test is made to determine whether another candidate device exists on the subnet at block484. If so, the process returns to block424to process the next device. Once all devices have been addressed, the process ends at block488.

FIG.5illustrates an example embodiment of a template500, suitably forming template136ofFIG.1. Device information is either native to the device or added from a database as noted above. Illustrated device information includes model number504, asset ID506, serial number512and service number516. Other service information, such as automated toner shipment notification520, may also be supplied. Template500also displays QR code524, suitably generated in the process ofFIG.4, along with instructions to scan it. Contact information is suitably supplied to assist users if needed. Instructions532are included directing users to affix device information to the MFP once scanning of the QR code has been completed.

FIG.6illustrates an example embodiment of an asset tag600suitably fixed on an exterior of a registered device. Device information includes model number604, asset ID608, serial number612, service contact information616and additional information620, such as automated toner shipment notification.

FIG.7illustrates an example embodiment of device registration using a smartsheet700, suitably generated on an MFP touchscreen display. This suitably supplies confirmed or updated information for devices for which tags have been provided. Supplied smartsheet information may include inputting a serial number at block704, a model number at block708, and location information such as device address at block712and device room at block716. Contact information may be input at block720and tag information supplied at block724. A user may request a copy of their submitted information to be sent to their contact address by checking block728before submitting their information by selecting submit button732.

FIG.8illustrates an example embodiment of asset assessment workflow800. A generated and displayed asset template804leads to an email808to commence smartsheet device registration812as illustrated in connection withFIG.7, above.

FIG.9illustrates an example embodiment of asset sticker workflow900. Asset tag management system904obtains device information908to generate template912. Template912is printed and then imaged, suitably by scanner914and leads to generation of smartsheet918. Resultant tags are suitably displayed in tag holder922as appears with displayed tag924.

FIG.10illustrates an example embodiment wherein asset tag1000includes QR code1004in addition to device information1008. Scanning of QR code1004results in generation of a smartsheet1008on a device touchscreen display to facilitate quick orders, such as consumables such as paper, ink or toner.

FIG.11illustrates an example embodiment of an asset assessment workflow which proceeds from asset tag management system1104which obtains device information1108to generate template1112. This template is scanned at1116and leads to generation of smartsheet1170.

While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the spirit and scope of the inventions.