JP2005535543A - System and method for providing asset management and tracking functions - Google Patents

Abstract

The process is designed to manage shipping items from companies and third parties to customer specified locations. The components of this system include electronic asset identification devices, central data repositories, mobile computing environments, and associated software applications that support client-server systems or n-tier computer systems. Mobile computing environments include software that allows a user to physically locate assets, view asset information, and modify such information to reflect the latest asset status. This information can then be exchanged and synchronized across n-tier computer systems. In addition, various staff members involved in shipping arrangements can access information available on a computer network such as the Internet.

Description

  The present invention generally relates to systems and methods for managing the flow of physical assets between various enterprises. More specifically, the present invention relates to a method and system for creating and maintaining an up-to-date record of asset status and location information that can be shared among various staff using various computer technologies.

  Maintaining an accurate and up-to-date record of shipment delivery and status information has been an area of significant obstacle for many years for businesses shipping large quantities of products or materials to various customer locations. Conventionally, the maintenance of such shipment and delivery records has been required to follow a footprint by document regarding the shipment and delivery of the particular item. Unfortunately, much of the paperwork necessary to maintain the accuracy of the records is often missing, delayed, or terminated in error. In addition, information regarding the status of delivered items is usually not included in such information.

  One way to increase the ability to maintain an accurate record of the shipper requires attaching a unique computer readable identification code, such as a bar code, to each product shipment. By scanning these codes at various intermediate points during delivery, a record of the shipping process can be maintained. This information can then be transferred to a database shared for subsequent access by authorized parties. Unfortunately, this process requires an aggressive step of locating and scanning with each identification code in a timely manner. Furthermore, this process does not assist product recipients in determining the location and status of received deliveries.

  Alternatively, container tracking methods have been developed that monitor shipments more automatically and continuously. Such systems may utilize high performance GPS (Global Positioning Satellite) systems as well as other electronic technologies to obtain real-time data at locations in transit. In addition to such a shipment tracking system, a system that enables monitoring and management of various inventory management systems is also introduced. By providing accurate and up-to-date information, the inventory management system allows businesses to easily determine the extent of their inventory. Unfortunately, such real-time systems are often costly to implement, especially when a large number of items are included in each shipment. Furthermore, similar to the code scanning system described above, these methods cannot provide information regarding the status of delivered goods.

  For example, in the normal sale and shipment of merchandise transactions, the carrier can know from the satellite tracking system that the container has arrived at the factory or site, but can not accept merchandise with damaged containers or other unacceptable merchandise. I don't know if it contains. Furthermore, although the shipment is actually received, this information is limited to the carrier and the staff who actually receives the shipment. Other staff who need this information as well are unaware of the delivery.

  In addition to the relatively simple case described above, there may also be some other situations that require accurate knowledge of both shipping location and status information in a timely manner. For example, there are situations where a manufacturer is required to deliver a material purchased under a purchase contract to a customer-specified location at a specific time. To fulfill these contractual obligations, manufacturers manufacture and ship the materials necessary to fulfill the contract, or purchase through third parties. In these cases, it is essential that the manufacturer maintain a logistics system that can coordinate the shipment of materials from the company and various third-party suppliers to avoid breach of this contractual obligation. . This logistics function requires timely tracking of the material from the shipping point to the destination. In addition, detailed information about the material following the delivery is also needed to provide a quick response to any possible delivery exception. This information can include items such as material descriptions, quantities, suppliers, purchase information, and the like.

To address these known issues, past attempts have used radio frequency identification (RFID) devices that track retail merchandise for asset security. The secondary use of such RFID devices was for near real-time tracking of material location. These RFID devices track using a bi-fixed “reader” system where the reader identifies the device within its predetermined neighborhood. In addition, RFID-reading hardware carried by humans is also being used, in which case the reader is equipped with a plurality of RFID-tagged tags, for example in a storage location or warehouse, or within the scope of such tagged assets. Physically moved by assets. Unfortunately, existing solutions do not provide a sufficiently robust and cost effective solution to the above problem.
US Pat. No. 6,614,349

  Accordingly, there is a need in the art for asset management and tracking systems for methods and systems that enable material tracking in an automatic, cost effective manner from point of delivery to point of delivery. Furthermore, there is a need for methods and systems that provide more detailed information in addition to material shipment and tracking information. Furthermore, there is a need for a method and system for enabling identification of specific materials among multiple materials. There also remains a need in the art for systems and methods that provide asset management and tracking information in a manner suitable for use in miniaturized resource computer systems. There is a further need for a method and system for enabling monitoring and exchange of environmental and operational status information.

  The present invention overcomes the problems described above and uses n-tier based computing such as radio frequency and other asset identification devices, distributed mobile computing systems, centralized data storage environments, and client server systems. Other advantages are obtained by providing a comprehensive method and system for managing bulk and non-bulk materials and assets. In particular, the new process is designed to manage shipping items from companies and third parties to customer specified locations. The components of this system include electronic asset identification devices, central data repositories, mobile computing environments, and associated software applications that support client-server or n-tier computing systems.

  According to one embodiment of the present invention, the various system components are electrically linked to each other to send and receive data related to the asset material being tracked. The general data tracked can include material identification information, material description, purchase details, storage and maintenance details, and material location and destination information.

  According to a second embodiment of the present invention, the central data repository is further electrically linked to a plurality of legacy database systems to maintain the accuracy of information on such systems in terms of confirmed shipping information. Is done. In this way, information is collected from a variety of different systems and synchronized with each other by the interaction of the central data repository and the mobile computing environment.

  According to another embodiment of the present invention, the mobile computing environment allows users on the site to physically locate asset material, view specific asset information, and accurately reflect this information to the latest status of the asset. Includes software that can be modified to. Further, the mobile computing environment can be linked with a central data repository across n-tier computing systems to synchronize data across the entire system.

  According to yet another embodiment of the present invention, various staff members associated with shipping arrangements can access information available on a computer network such as the Internet. In this way, the staff can easily check the status of various shipments and respond quickly based on the information collected during any status update, and what can happen by this. Solutions to possible exceptions are also handled quickly.

  According to another embodiment of the present invention, the electronic asset management device can be further configured to include various types of sensors. As a result, these devices can operate to process and store sensor output information for subsequent relaying to the user via a mobile computing environment or other means. In addition, such intelligent detection devices can also be used to relay environment and operating status information independently in a wireless manner, thereby creating a virtual network of intelligent detection devices and outputting their output. It can be analyzed collectively.

  According to another embodiment of the present invention, the database management function is implemented and the database of information exchanged and synchronized with the handheld computer and material management database is sized and structured to allow efficient operation in a field environment. Is minimized.

  The invention may be more fully understood by reading the following detailed description of the preferred embodiment in conjunction with the accompanying drawings.

  Referring now to the drawings, and more specifically in FIG. 1, a general block diagram illustrating an asset and material management system 100 configured in accordance with one embodiment of the present invention is shown. In particular, in the simplest implementation, the asset and material management system 100 of the present invention comprises at least an asset management server computer system 102, a remote client computer system 104, and at least one query device 106 (either handheld or stationary). including. In addition, each item or asset to be managed includes an electronic asset identification device, such as an RFID device (not shown).

  By implementation of one embodiment of the system, an RFID device or tag is attached to each asset to be tracked (eg, crate, storage container or packaging container, or the like) at the point of shipment. An electronic association is made between each RFID tag and the material being shipped, which is then automatically transmitted to the asset management server computer system 102. Interrogation of RFID devices with either fixed or mobile radio frequency interrogator (reader) 106 as well as status events (eg port entry, arrival at the site, etc.) as material moves from the point of delivery to the destination With these ID associations, the latest information at that location along the route can be recorded automatically and remotely. This information is then typically shared with the client computer system 104 and then up-to-date information regarding material status or placement can be returned to the asset management server computer system 102 in wired or wireless mode. Detailed information about the material being tracked can be obtained by accessing the asset management server computer system 102 by querying a client server type system or by a mobile computing device.

  One element of this solution is the use of electronic asset identification devices such as RFID to track asset materials. These devices can be programmed before or during use. Such programming can include associating the device with an electronic identification code, which can be alphanumeric. These devices are configured to transmit this code as well as other information upon request from a specially designed RFID interrogator (reader). As summarized above, these readers can be used in either fixed or mobile environments. When a device with an electronically encoded ID is associated with the material to be tracked, other relevant data is tracked with the material shipment tracking data using a centralized or decentralized data repository. be able to. This data when packaged in an organized manner can be viewed and modified via a mobile computing device that can also allow interaction with the asset identification device. These devices can then directly or indirectly synchronize their latest information with the asset management server computer system 102 using either a wireless or wired connection communication system.

  In addition to viewing via a mobile computing device, the system also tracks material by another client computer system (not shown) that is electronically connected to the asset management server computer system via a computer network. Provide seamless viewing and modification of data related to identification, usage. Up-to-date material data information can be viewed in a near real-time environment by connection of the mobile computing system to the asset management server computer system. The electronic asset identification device provides a remote automatic means for tracking and updating the status of the material.

  As will be described in more detail below, the “Materials Management” web application that interfaces with the asset management information described above is accessible to designated staff. Furthermore, updates to the asset management server computer system can be achieved by using a mobile handheld computing platform and a specially designed software package called “TagDetect”.

  The asset management server computer system 102 is, for example, Microsoft Windows (registered trademark) NT (registered trademark), Windows (registered trademark) 2000, Windows (registered trademark) XP (registered trademark), Unix, Linux, Xenix, IBM AIX (registered trademark). ), Hewlett-Packard UX (registered trademark), Novell Network (registered trademark), Sun Microsystems Solaris (registered trademark), OS / 2 (registered trademark), BeOS (registered trademark), Mach, Apache, OpenStep (trademark), or others Can be, or can include, a workstation running any suitable operating system or platform. In operation, the asset management server computer system 102 executes at least one web server application conventionally known as an HTTPd server. In addition, the asset management server computer system 102 may store local storage for at least one, usually many web pages, as files in HTML format, XML (Extensible Markup Language) format, and / or other formats. It is preferable to provide. The asset management server computer system 102 may also include a number of individual server computers or database computers located at various locations on the network.

  The client computer system 104 is, for example, Microsoft Windows (registered trademark) 95, 98, Millenium (registered trademark), NT (registered trademark), XP (registered trademark), or 2000, Windows (registered trademark) CE (registered trademark). , PalmOS (R), Unix, Linux, Solaris (R), OS / 2 (R), BeOS (TM), MacOS (TM), or any other operating system or platform that includes a personal computer Can do. The client computer system 104 may be an Intel x86-based device, Motorola 68K or PowerPC (registered trademark) device, MIPS, Hewlett-Packard Precision (registered trademark), or Digital Equipmemt Corp (DEC) Alpha (registered trademark) RISC processor. Microprocessors, microcontrollers, or other general purpose or special purpose devices that operate under program control. In addition, the client computer system 104 may include electronic memory, such as RAM (Random Access Memory) or EPROM (Electronically Programmable Read Only Memory), hard drive, CD-ROM or writable / re-writable CD-ROM, DVD-ROM or writable / rewritable DVD-ROM or other storage device such as magnetic, optical, or other media, and other connected via an electronic bus as will be understood by those skilled in the art Related components may be included. The client computer system 104 is a network-enabled device such as a WebTV (trademark) unit, a wirelessly available Palm (trademark) Pilot or similar unit, a set top box, a Sony PlayStation (trademark) or a Playstation 2 (trademark). ), Microsoft X-Box (registered trademark), Nintendo GameCube (registered trademark), Sega Dreamcast (registered trademark) or other network-capable gameplay consoles, browser-equipped mobile phones, or other TCP / IP-enabled clients or Other devices can be included.

  The interrogation device 106 is a handheld computer such as Palm® Pilot, Compaq iPAQ®, Sony Clie, Handspring Visor, Research in Motion Blackberry, or Windows for transmitting and receiving radio frequency signals to and from the electronic asset identification device. Similar devices running on CE® or PalmOS can be included. In addition, the interrogation device 106 may include a dedicated stand-alone fixed reading device.

  Suitable computer networks for use with the present invention include, for example, a local intranet, a PAN (personal area network), a LAN (local area network), a WAN (wide area network), a MAN (metropolitan area network), a virtual private network ( VPN), storage area network (SAN), frame relay connection, advanced intelligent network (AIN) connection, synchronous optical network (SONET) connection, digital T1, T3, E1, or E3 line, digital data service (DDS) connection, DSL (Digital subscriber line) connection, Ethernet (registered trademark) connection, ISDN (integrated service digital network) line, V. 90, V.I. 92, V.I. 34 or V.I. Includes any one or more of dial-up ports such as 34bis analog modem connections, cable modems, ATM (Asynchronous Transfer Mode) connections, or FDDI (Optical Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connections Or can be connected to these.

  In addition, computer networks also include WAP (Wireless Application Protocol), GPRS (General Packet Radio Service), GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access), mobile phones Network, GPS (Global Positioning System), CDPD (Cellular Digital Packet Data), RIM (Research In Motion) Duplex Paging Network, Bluetooth Radio, IEEE802.11x based radio frequency network, or HPNA (Home Phone Line Network Standard) A link to any of a variety of wireless networks can also be included, including compliant Ethernet networks. The computer network further includes RS-232 serial connection, IEEE-1394 (Firewire (registered trademark)) connection, optical channel connection, IrDA (infrared) port, SCSI (small computer system interface) connection, USB (universal serial bus) connection, Alternatively, any one or more of other wired or wireless digital or analog interfaces or connections may be included or connected.

In general operation, the client computer system requests a web page by issuing a URL request to the server system 102 over the network. A URL consistent with the present invention can be a simple URL of the following format:
<Protocol_identifier>: // <server_path> / <web_page_path>
The protocol identifier “http” specifies a conventional hypertext transfer protocol, but other suitable protocol identifiers may be implemented. For example, a URL request for a secure network communication session typically utilizes a secure protocol identifier “https”, assuming that the client browser and web server each support and execute a secure socket layer (SSL). “Server_path” is generally in the form of “prefix.domain”, where the prefix can be “www” to specify a web server, where “domain” is a standard network subdomain. It is a top level domain of the server system 106. An optional “web_page_path” is provided to specifically identify a particular hypertext page maintained by the asset management server computer system 102.

  In response to the received URL identifying the existing web page, the asset management server system 102 returns a web page according to the HTTP protocol to the client computer system 104. This web page typically includes text and graphic information, including embedded hypertext links, usually called hyperlinks, that allow the client user to easily select the next URL for outgoing to the computer network. Both are incorporated. In this way, multiple individual web pages can be combined into a comprehensive website.

Also, the URL issued from the client computer system 104 can be in a complex format that identifies a common gateway interface (CGI) program on the server system 106. Such HTML hyperlink references can take the following form:
<Form action = “http://www.vendor.com/cgi-bin/logon.cgi” method = post>
This form of hypertext link is a response to logon. Instructs execution of cgi program or script. Logon formats supported by the logon CGI program are typically used to obtain client user login names and passwords, for example between client browsers and web servers for the purpose of supporting the exchange of security or other privileged information. In between. In addition, website privileges can be managed by referencing information received during such logon requests, which allows for specific customization of the site for a unique individual or class of individuals. .

  Referring to FIG. 2, a block diagram illustrates a second more specialized embodiment 200 of the asset management system of the present invention. Specifically, the asset management system of FIG. 2 includes three main areas: an initial asset information area 202, a web application area 204, and a project site area 206. Each of these areas plays a role in the overall system and interacts with each other through various computer network technologies.

  Referring now to the initial asset information area 202, a tagging computer system 208 is provided that includes at least RFID tag writing software for formatting RFID tags prior to placement on various assets to be tracked. In one embodiment, the computer system 208 identifies the various assets that are incorporated into each RFID tag, such as project information that will use the asset, as well as other information about the asset, such as predictive information storage requirements. It is preferably networked to an existing legacy database 209 for retrieving information. Furthermore, in another embodiment, when a single tag is used to identify several shipped items, the computer system 208 also sends an electronic packing list to both the RFID tag as well as the web application area 204. Can operate to. Other details regarding this embodiment are provided in further detail below.

  Tag writer device 210 is operatively connected to computer system 208 to write information formatted by computer system 208 onto RFID tag 212. The tag 212 is then secured to the associated asset 214 using any suitable means such as an adhesive or the like. Once the RFID tag 212 is secured to the asset 214, the asset is placed and shipped to the site destination by any desirable means. It should be understood that the initial asset information area includes both internal and third party shipping procedures. Of course, if the shipment is from a third party, the connection to the legacy database can be different depending on how the information contained within the RFID tag was generated. Regardless, information regarding RFID tag identification information and packing list data is exchanged with the web application area 204 for inclusion in the system. In one embodiment, data transfer between the initial asset information area 202 and the web application area 204 is realized by ftp (file transfer protocol) transfer.

  As summarized above, once information is shared between the tag writing computer system 208 and the web application area 204, this information is available on the Internet or other suitable computer network. Made available for viewing and modification through the application. Furthermore, when data transfer between the legacy database system 209 and the web application area 204 is achieved, specific information about the various tracked assets and the projects they are part of is also available on the computer network. It is.

  In the illustrated embodiment, the web application area 204 includes several elements. Initially, all RFID tag, asset, and project information is received and stored in the material management database system 216. This information is then made available to the web application server 218 and the connected HTTP server 220 for distribution over a computer network. As will be described in more detail below, web applications and HTTP servers provide this information in a user-specific manner utilizing multiple interactive web pages. Further, it should be understood that the connection of the web application server to the material management database system 216 is bi-directional. That is, asset management information updated via a web application server, either directly or through an interactive web application using a handheld computing device described in detail below, is for subsequent retrieval by the next user. And written in the material management database system accordingly.

  Optionally, as shown, the web application can also include an authentication server 222 that can access the LDAP directory system 224 to facilitate user login and authentication. Along with such a system, various web application functions can be provided to various users according to user login information.

  Next, in the project site area 206, interaction with site staff can easily determine up-to-date information about the asset being tracked and upload it to a web application and material management database system for review on a computer network. . In particular, when a tracking asset 214 with an RFID 212 is received in the field, information about the asset can be uploaded to the web application area 204 by site staff in various ways, such as direct web entry and handheld synchronization. Initially, a handheld device 226, such as a device running a Windows CE or PalmOS operating system, is typically provided with RFID tag reading capability by adding both a hardware module and a corresponding software application. Whether using the handheld device 226 and a software application, the asset handler will actively read information from the located asset or locate an asset contained in multiple tagged assets Either of these can be done.

  Once the asset is located, other information regarding the status of the asset can be entered into the handheld device application for future uploads to the web application area 204. The entry of this information is simplified by a GUI on the device 226 that specifically allows entry of various information such as asset receipt, maintenance information, and other asset identification and project data. Additional details and specific embodiments of the handheld device application are described in detail below with reference to FIG.

  Next, during synchronization with the connected on-site computer system 228, information on the device 226 regarding the one or more assets located and updated is added and / or within the on-site computer system 228. Is synchronized with the information contained in In the preferred embodiment, this information is exchanged in the form of an XML file, which is an additional data format such as a comma-separated (separated) value or any other suitable data format, but at the time of uploading the web application Area 204 is intended to provide simple parsing of the data contained therein.

  When information is synchronized between the handheld device 226 and the on-site computer system 228, the information also requires synchronization between the on-site computer system 228 and the web application area 204. This process is completed upon login to the web application server system 218 by site staff. Upon access and authentication by the authentication server 222, the user is provided with an option to synchronize these data with the website. Thus, information synchronized between the on-site computer system 228 and the handheld device 226 is transmitted to the web application server 218, and subsequently for both relaying to legacy systems and viewing or modification via the web application. To the material management database system 216. In addition, as summarized above, the project site staff may also have the option to enter asset status information directly into the web application without synchronization. This allows site staff to perform simple status updates without having access to the appropriate handheld device. Furthermore, file exchange between a web application and a client computer or handheld device is public key encryption, message hashing, or the like so that the data transmitted between them is not intercepted by unauthorized parties. It can be encrypted using known encryption techniques such as those.

  According to another embodiment of the invention, various access to the web application is provided depending on the type of user login to the application. User types can include internal business management staff, on-site material handling staff, exception resolution staff, business staff, on-site customer management staff, and customer headquarters staff. The differences between application access and privileges are described for each of these types in further detail below.

  Referring now to FIG. 3, a flow diagram is shown that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information over a computer network such as the Internet. In the following figure, each step of the described process illustrates a decision made by a user visiting a website maintained by the web application area 204 described in detail above. First, when a URL related to a website in the web application area is input, the home page 300 is displayed to the user. Prior to logging in to gain access to specific asset information, the user can select multiple management pages, such as contact page 302, that facilitate communication with the website operator. When the user logs in (can be selected from either the home page or the management page), a main menu 304 is displayed to the user including various options for displaying and modifying asset management information. In accordance with an embodiment of the present invention, the web application area uses information provided during user login to determine various options available to the user. In this way, the user is directed to the information for which the view is permitted.

  Among the options provided to the user, this embodiment includes an option to retrieve records by both a specific asset number as well as a project. Further, when viewing a project, the user is given the option of either viewing the details of the project or searching for assets within the project. It should be understood that the project relates to the collection of assets relating to identified customer operations, such as, for example, power plant generators. In this example, the project may include a listing of all generator assets. In addition, a project can also include unit subcategories, where various units comprise a project, and each unit has various assets.

  In response to the user selection of the project selection option, a project details page 306 is displayed. This page provides the user with the option to search for information about the project, as well as project assets, list project assets by unit, and view the unit status page 307. In response to a user selection for project asset search, an asset search form 308 is displayed to the user, either from the main menu 304 or the project details page 306, where search criteria for the asset can be entered. In response to the transmission of this form, an asset search result page 310 showing various assets that match the transmitted search conditions by item is displayed.

  From this point on, the user has three options: return to the project details page 306, view details of the selected asset on page 312 or the identified asset in the form on page 314 Can be confirmed or rejected. With respect to the asset detail page 312, when the user views the current details and status of the asset, the user proceeds to the asset receipt confirmation form 314 or associated with the asset, such as the packing list detail page 316 or the storage / maintenance requirements page 318. You have the option to view more details. With respect to the asset receipt confirmation or rejection form on page 314, the user completes and sends a form indicating either asset receipt confirmation or rejection. When the asset is received and accepted, a receipt confirmation page 320 is displayed. However, if the asset is rejected, an asset rejection form 322 is displayed to indicate to the user the reason for rejection, thereby creating an exception in the asset management system. This asset exception confirmation is then displayed to the user on page 324. Once the identified asset is accepted or rejected, the user can return to the asset detail page 312 from which the user returns to the project detail page 306 to select another asset for review. Can do.

  With reference to FIGS. 4-9, there are shown flow diagrams that schematically illustrate some other embodiments of a method for sharing and accessing asset tracking information over a computer network, such as the Internet. As explained above, various privileges and site access are granted depending on the identity of the user, thereby changing the overall content of the site for different types of users. Accordingly, each of FIGS. 4-9 illustrates the method of the present invention for a plurality of different types of users. FIG. 4 particularly relates to website management level staff having access to substantially all possible areas of the website. FIG. 5 specifically relates to website access provided to project site material handling staff (eg, shipping receipt staff, etc.). FIG. 6 specifically relates to supplier exception resolution staff to enable access to asset exceptions and other project / asset information, FIG. 7 specifically relates to supplier project team business, and FIG. Regarding the customer-side project site management staff, FIG. 9 particularly relates to the customer-side high-level management staff.

  Referring now to FIG. 4, this embodiment includes additional options specifically related to the synchronization process described above and available to website management level users. However, as described above, when a URL related to a website in the web application area is input, the home page 400 is displayed to the management user. Again, some options are available to the administrative user at this point. Prior to logging in to gain access to user-specified asset information, the administrative user can provide a help page 402, a site map 404 showing the layout of the website, a contact page 406 to facilitate communication with the website operator, And multiple management pages such as feedback form 408 and associated send page 410 may be selected. The administrative user can select login to the site from either the home page 400 or the administrative pages 402-410. In response to this selection, a login form 412 is provided to the administrative user to receive login information, such as a username and password combination. Subsequently, this information is received and processed in the manner outlined above to determine the level of site access to which the administrative user is given. If it is determined that the login information is inaccurate, an appropriate error message page 414 prompting re-input of information is displayed. Following entry of the appropriate login information, a main menu 416 is displayed to the administrative user including several options including synchronization options, report view options, search options by asset number or RFID tag number, and project selection options. .

  Specifically with respect to synchronization options, management level users are authorized to synchronize asset management information between the website and the remote client computer system in the manner detailed above. In particular, by selecting a synchronization option from the main menu page 416, a synchronization selection form 418 is displayed where information regarding the information to be synchronized is transmitted. This information should include at least the local file location for the XML file described above that is later uploaded to the website. Next, when the completed form 418 is sent, an email message 420 is created confirming the synchronization process.

  Returning to the main menu 416, the administrative user can also select a report view option. Selecting this option results in the report menu page 422 being displayed, which includes a listing of available reports, including exception reports and maintenance reports. If the user selects an exception report option, an exception report creation page 424 is displayed, which preferably includes options regarding the format and content of the created exception report. Once the selection is made, the created exception report is displayed to the user on page 426. Further details regarding all exceptions listed in the report are then available on page 428.

  If the user selects a maintenance report option, a maintenance report creation page 430 is displayed, which preferably includes options regarding the format and content of the maintenance report to be created. A maintenance report is then created for the various asset management information collected for any required or proposed maintenance performed on any asset. Once selected, the maintenance report to be created is displayed to the user on page 432.

  Returning to the main menu 416, the administrative user can also select a view of the project or asset specific information in various ways. Initially, the user can simply enter an asset identification number or RFID tag number and choose to view the asset associated with that number. In the preferred embodiment, this number can be entered directly on the main menu 416. The transmission of this number will then display the corresponding assets in various formats, including the default format on page 434, the logistics format on page 436, the customer format on page 438, and the inventory management format on page 440. become. Furthermore, transitions between any available formats are easily made from any other format result. Once the asset search results are displayed, the user then has the ability to accept or reject the asset listed on page 442, the ability to view additional information about the asset selected on page 444, or pages 435, 437, 439. , And 441 with the ability to export search results to an external spreadsheet application in the desired format, each of these pages corresponding to the selected search result format. Additional information regarding the content of asset receipt page 442 and asset detail page 444 is described in further detail below.

  Returning to the main menu 416, the user can also retrieve asset management information by selecting an available project. When this option is selected, a list of available projects is displayed on page 446. From this location, the user views on page 448 the project level detailed information including a listing of all assets related to the selected project, searches for assets contained within the project on page 450, and further on page 452. You can choose to view the asset exception listing for the selected project. Specifically looking at page 448, when project level detailed information is displayed for the selected project, the user has several options available for displaying additional information. Initially, the user can select to display an asset search page 450 to further narrow the number of available assets, or the asset exception listing page 452 described above. In addition, the user has the option to select a particular asset or collection of assets and view this information in the various formats described on pages 434-440. In addition, from the project details page 448, the user also has the option to view project level prediction information on page 453 as well as status information for various units included in the project. With respect to prediction information, when this option is selected, a material list prediction page 454 is displayed that includes various prediction information regarding the number of assets associated with the project, the size of the assets, and the like. At this point also a selection is provided to view the asset specific forecast information. When this is selected, an asset prediction page 456 is displayed.

  Returning to the asset search form on page 450 and selecting this page from either the project selection page or the project details page, information about a particular asset or requested asset is transmitted. At this point, a decision can be made on page 458 to export all matching asset information to an external spreadsheet application. In other cases, when an asset search form is submitted on page 450, the resulting asset information is displayed in various formats as shown above with respect to pages 434-440.

  Returning to page 442 regarding asset receipt / rejection, at this point the user can select to confirm receipt of the asset on page 460 or enter an acceptance exception. If the asset is received without exception, the user is simply returned to the asset search results page (434-440). However, if an exception is entered, an asset exception annotation page 462 is displayed to the user. At this point, the user enters the exception information and sends this information on page 464. If the exception is related to a shortage of assets received, the specific status is entered and the asset shortage creation page 466 is displayed. In other cases, the user is returned to the asset receipt page 442. If deficiency information is generated, additional information regarding deficiencies is transmitted on page 468 and the user returns to page 442 of the asset receipt form, or if asset deficiency information is generated after asset receipt, the user Can proceed to the asset detail page 444.

  From the asset detail page, the user also has various additional options, can enter an asset exception on page 462, receive assets on page 442, and modify or locate asset location information on page 472. The asset storage maintenance details can be viewed on page 470, and the asset packing list details information can be viewed on page 474. With respect to the asset location page 470, when this page is displayed, any corrections to asset location are made and transmitted on page 476. With respect to the asset storage maintenance details page 472, the administrative user can also select to view and / or modify the maintenance log of received assets. In this case, a maintenance log page 480 showing the current status of the asset maintenance log is displayed along with an option to create and / or modify the displayed log. If a log modification is required, the user opens the maintenance log modification page 482 and sends any requested modifications. Similarly, if a new input is to be created, the user selects a creation option and opens a maintenance log creation page 484 where the information for the new input is sent.

  The user can then return to the asset exception listing page 452 and the user can select the listed exception, and can proceed to the asset exception details page 486 if it is not a missing exception. From this page, the user can select a resolution for the selected asset exception. In this case, the asset exception solution page 478 is displayed. The user can then return to the asset exception details page 486 indicating that the exception has been resolved. In the case of a shortage exception, an asset shortage detail page 488 is displayed. When the management user wants to end the shortage information, the asset shortage close page 490 is displayed, and subsequently transmitted, and the user is returned to the asset exception list display page 452.

  By utilizing the collection of various interactive web pages described above, an administrative user can easily update and view asset management information at any level of the website. In addition, the user can synchronize this data with data maintained on the remote client computer system.

  Referring now specifically to FIG. 5, this embodiment includes additional options that are particularly relevant to the synchronization process described above, and options that are available to project site material handling staff (eg, shipping receipt staff). including. As shown in FIGS. 3 and 4 above, when a URL related to a website in the web application area is input, a home page 500 is displayed to the material handling user. Again, several options are available at this point for material handling users. Prior to logging in to gain access to user-specific asset information, the material handling user has a help page 502, a site map 504 showing the layout of the website, and a contact page 506 to facilitate communication with the website operator. In addition, a plurality of management pages such as feedback form 508 and associated send page 510 may be selected. From either the home page 500 or the management pages 502-510, the material handling user can select to log in to the site. In response to this selection, a material handling user is provided with a login form 512 for receiving login information, such as a username and password combination. Subsequently, this information is received and processed in the manner outlined above to determine the level of site access granted to material handling users. If it is determined that the login information is inaccurate, an appropriate error message page 514 prompting re-input of information is displayed. Following entry of appropriate login information, a main menu 516 is displayed to the material handling user, including several options including data synchronization options, search options by asset number or RFID tag number, and project selection options.

  Specifically with respect to synchronization options, material handling level users are authorized to synchronize asset management information between the website and the remote client computer system in the manner detailed above. In particular, by selecting a synchronization option from the main menu page 516, a synchronization selection form 518 is displayed where information regarding the information to be synchronized is transmitted. This information should include at least the local file location for the XML file described above that is later uploaded to the website. As discussed above, this information can be generated in response to client synchronization between the remote client computer system and the material handler's handheld device. Next, when the completed form 518 is sent, an email message 520 is created confirming the synchronization process.

  Returning to the main menu 516, the material handling user can also select a view of the project or asset specific information in various ways. Initially, the user can simply enter an asset identification number or RFID tag number and choose to view the asset associated with that number. In the preferred embodiment, this number can be entered directly on the main menu 516. The transmission of this number will then display the corresponding asset in various formats including the default format on page 534, the logistics format on page 536, and the inventory management format on page 538. Furthermore, transitions between any available formats are easily made from any other format result. Once the asset search results are displayed, the user then has the ability to accept or reject the asset listed on page 542, the ability to view additional information about the asset selected on page 544, or pages 535, 537, and 539 has the ability to export search results to an external spreadsheet application in the desired format, each of these pages corresponding to the selected search result format. Additional information regarding the content of asset receipt page 542 and asset detail page 544 is described in further detail below.

  Returning to the main menu 516, the user can also retrieve asset management information by selecting an available project. When this option is selected, a list of available projects is displayed on page 546. From this position, the user views on page 548 detailed project level information including a listing of all assets associated with the selected project, searches for assets contained within the project on page 550, and in step 552 You can choose to display a list of asset exceptions for the selected project. Specifically looking at page 548, when project level detailed information is displayed for the selected project, the user has several options available for displaying additional information. Initially, the user can choose to display an asset search page 550 to further narrow the number of available assets, or the asset exception listing page 552 described above. In addition, the user has the option to select a particular asset or collection of assets and view this information in the various formats described on pages 534-540. In addition, from the project details page 548, the user also has the option to view project level prediction information as well as status information of various units included in the project. Unit status information is displayed on page 553. With respect to forecast information, when this option is selected, a material list forecast page 554 is displayed that includes various forecast information regarding the number of assets associated with the project, the size of the assets, and the like. At this point, a choice to view the asset specific forecast information is provided. When this is selected, an asset prediction page 556 is displayed.

  Returning to the asset search form on page 550 and selecting this page from either the project selection page or the project details page, information about a particular asset or required asset is transmitted. At this point, a decision can be made on page 558 to export all matching asset information to an external spreadsheet application. In other cases, when an asset search form is submitted on page 550, the resulting asset information is displayed in various formats as shown above with respect to pages 534-538.

  Returning now to page 542 for asset receipt / rejection, at this point the user can choose to confirm receipt of the asset on page 560 or enter an acceptance exception. If the asset is received without exception, the user is simply returned to the asset search results page (534-538). However, if an exception is entered, an asset exception annotation page 562 is displayed to the user. At this point, the user enters exception information and transmits this information on page 564. If the exception is related to a shortage of assets received, a specific situation is entered and an asset shortage creation page 566 is displayed. In other cases, the user is returned to the asset receipt page 542. If deficiency information has been generated, additional information regarding deficiencies is transmitted on page 568 and the user returns to the asset receipt page 542, or if deficiency information has been generated after receipt of the asset, the user will receive asset details. You can proceed to page 544.

  From the asset detail page, the user can also have various additional options, enter an asset exception on page 562, receive an asset on page 542, and modify or locate asset location information on page 570. The asset storage maintenance details can be viewed on page 570 and the asset packing list details information can be viewed on page 574. With respect to the asset location page 572, when this page is displayed, any corrections to asset location are made and transmitted on page 576.

  The user can then return to the asset exception details page 552 and the user can select the listed exception and, if not a missing exception, can proceed to the asset exception details page 586. In the case of a shortage exception, an asset shortage detail page 588 is displayed.

  By limiting the available collection of interactive web pages described above, material users can easily update and view the appropriate asset management information without accessing information outside the scope of their duties. Can do.

  Referring now specifically to FIG. 6, the present embodiment is particularly concerned with website options available to users at the supplier's exception resolution level. However, as described above, when a URL related to the website in the web application area is input, the home page 600 is displayed to the supplier-side exception resolution user. Again, some options are available to the supplier exception resolution user at this point. Prior to logging in to gain access to user-specific asset information, the supplier-side exception resolution user can help page 602, site map 604 showing the layout of the website, to facilitate communication with the website operator. A plurality of management pages can be selected, such as a contact page 606 and further a feedback form 608 and associated send page 610. From either the home page 600 or the management pages 602 to 610, the supplier-side exception resolution user can select login to the site. In response to this selection, a supplier form exception resolution user is provided with a login form 612 for receiving login information such as, for example, a username and password combination. Subsequently, this information is received and processed in the manner outlined above to determine the level of site access provided to the supplier exception resolution user. If it is determined that the login information is inaccurate, an appropriate error message page 614 prompting re-input of information is displayed. Following entry of the appropriate login information, a main menu 616 is displayed to the supplier exception resolution user including several options including a search option by asset number or RFID tag number, and a project selection option.

  Specifically for the search option by asset number or RFID tag number, the user simply enters the asset identification number or RFID tag number. In the preferred embodiment, this number can be entered directly on the main menu 616. The transmission of this number will then display the corresponding asset in various formats, including the default format on page 634, the logistics format on page 636, and the inventory management format on page 638. Furthermore, transitions between any available formats are easily made from any other format result. Once the asset search results are displayed, the user then exports the search results to an external spreadsheet application in the desired format on pages 635, 637, 639, or the ability to view additional information about the selected asset on page 644. Each of these pages corresponds to the format of the selected search result. From asset detail page 644, the user can also view asset packing list detail information on page 674.

  Returning to the main menu 616, the user can also retrieve asset management information by selecting an available project. When this option is selected, a list of available projects is displayed on page 646. From this location, the user views on page 648 detailed project level information including a listing of all assets associated with the selected project, searches for assets contained within the project on page 650, and further on page 652. You can choose to view the asset exception listing for the selected project. Specifically looking at page 648, when project level detailed information is displayed for the selected project, the user has several options available for displaying additional information. Initially, the user can select to display an asset search page 650 to further narrow the number of available assets, or can select an asset exception listing page 652. This option is particularly relevant to this particular type of user because it is the exception solution most relevant to the user. In addition, the user has the option to select a particular asset or collection of assets and view this information in the various formats described on pages 634-638. In addition, from the project details page 648, the user also has the option to view project level prediction information as well as status information for various units included in the project. For forecast information, when this option is selected, a material list forecast page 654 is displayed that includes various forecast information regarding the number of assets associated with the project, the size of the assets, and the like. At this point also a selection is provided to view the asset specific forecast information. When this is selected, an asset prediction page 656 is displayed.

  Returning to the asset search form on page 650 and selecting this page from either the project selection page or the project details page, information about a particular asset or required asset is transmitted. At this point, a decision can be made on page 658 to export all matching asset information to an external spreadsheet application. In other cases, when an asset search form is submitted on page 650, the resulting asset information is displayed in various formats as shown above with respect to pages 634-638.

  The user can then return to the asset exception details page 652 and the user can select the listed exception, and if not, can proceed to the asset exception details page 686. From this page, the user can select a resolution for the selected asset exception. In this case, an asset exception solution page 678 is displayed. The user can then return to the asset exception details page 686, indicating that the exception has been resolved. In the case of a shortage exception, an asset shortage detail page 688 is displayed. Next, the shortage status can be closed on page 690 for the displayed shortage. From this position, the user can proceed to the asset detail page 644.

  By utilizing the collection of various interactive web pages described above that are specifically customized to these needs, supplier exception resolution users can easily view and resolve asset exceptions as well as additional asset management information. it can.

  Referring now specifically to FIG. 7, the present embodiment includes additional options specifically for users at the supplier project team level. Again, when a URL associated with a website in the web application area is entered in the same manner as described above, the home page 700 is displayed to the supplier project team user. Similarly, several options are available at this time for supplier project team users. Prior to logging in to gain access to user specific asset information, the supplier project team user can help page 702, site map 704 showing the layout of the website, to facilitate communication with the website operator. A plurality of management pages can be selected, such as a contact page 706 and further a feedback form 708 and associated send page 710. From either the home page 700 or the management pages 702 to 710, the supplier project team user can select to log in to the site. In response to this selection, a supplier form project team user is provided with a login form 712 for receiving login information such as a username and password combination. Subsequently, this information is received and processed in the manner outlined above to determine the level of site access provided to the supplier project team user. If it is determined that the login information is inaccurate, an appropriate error message page 714 prompting re-input of information is displayed. Following entry of appropriate login information, a main menu 716 containing several options including synchronization options, report view options, search options by asset number or RFID tag number, and project selection options is displayed on the supplier side project team. Displayed to the user.

  Specifically for the report view option, selecting this option will display a report menu page 722 containing a listing of available reports, including exception reports and maintenance reports. If the user selects an exception report option, an exception report creation page 724 is displayed, which preferably includes options regarding the format and content of the created exception report. Once the selection is made, the created exception report is displayed to the user on page 726. Further details regarding all exceptions listed in the report are then made available on page 728.

  If the user selects a maintenance report option, a maintenance report creation page 730 is displayed, which preferably includes options regarding the format and content of the maintenance report to be created. A maintenance report is then created for the various asset management information collected for any required or proposed maintenance performed on any asset. Once selected, the maintenance report to be created is displayed to the user on page 732.

  Returning to the main menu 716, the supplier project team user can also select a view of the project or asset specific information in various ways. Initially, the user can simply enter an asset identification number or RFID tag number and choose to view the asset associated with that number. In the preferred embodiment, this number can be entered directly on the main menu 716. The transmission of this number will then display the corresponding asset in various formats, including the default format on page 734, the logistics format on page 736, and the inventory management format on page 738. Furthermore, transitions between any available formats are easily made from any other format result. Once the asset search results are displayed, the user then has the ability to accept or reject the asset listed on page 742, the ability to view additional information about the asset selected on page 744, or pages 735, 737, and 739 has the ability to export search results to an external spreadsheet application in the desired format, each of these pages corresponding to the selected search result format. Additional information regarding the content of the asset detail page 744 is described in further detail below.

  Returning to the main menu 716, the user can also retrieve asset management information by selecting an available project. When this option is selected, a listing of available projects is displayed on page 746. From this location, the user views on page 748 project level detailed information including a listing of all assets associated with the selected project, searches page 750 for assets contained within the project, and on page 752 You can choose to display a list of asset exceptions for the selected project. Specifically looking at page 748, when project level detailed information is displayed for the selected project, the user has several options available for displaying additional information. Initially, the user can select to display an asset search page 750 to further narrow the number of available assets, or the asset exception listing page 752 described above. In addition, the user has the option to select a particular asset or collection of assets and view this information in the various formats described on pages 734-738. In addition, from the project details page 748, the user also has the option to view project level prediction information as well as status information of various units included in the project. For forecast information, when this option is selected, a material list forecast page 754 is displayed that includes various forecast information regarding the number of assets associated with the project, the size of the assets, and the like. At this point, a choice to view the asset specific forecast information is provided. When this is selected, an asset prediction page 756 is displayed.

  Returning to the asset search form on page 750 and selecting this page from either the project selection page or the project details page, information about a particular asset or required asset is transmitted. At this point, a decision can be made on page 758 to export all matching asset information to an external spreadsheet application. In other cases, when an asset search form is submitted on page 750, the resulting asset information is displayed in various formats as shown above with respect to pages 734-738.

  Turning now to the asset details page 744, several options are available to the user at this point. If the shortage information needs to be inserted for a particular asset, the user selects the shortage option from the asset detail page 742, resulting in the asset shortage creation page 766 being displayed. Next, additional information regarding the deficiency is transmitted on page 768 and the user is returned to the asset detail page 744. In addition, asset shortage maintenance details can be viewed on page 770 and asset details page 744 allows asset packing list details to be viewed on page 774. With respect to the asset storage maintenance detail page 770, the supplier project team user may also select to view and / or modify the maintenance log for the received asset. In this case, a maintenance log page 780 showing the current status of the asset maintenance log is displayed along with an option to create and / or modify the displayed log. If a log modification is required, the user opens the maintenance log modification page 782 and sends any requested modification. Similarly, if a new input is to be created, the user selects a creation option and opens a maintenance log creation page 784 where the information for the new input is sent.

  The user can then return to the asset exception details page 752 and the user can select the listed exception and, if not a missing exception, can proceed to the asset exception details page 786. In the case of a shortage exception, an asset shortage detail page 588 is displayed.

  By utilizing the specific collection of various interactive web pages described above, supplier project team users can easily update and view the asset management information for which they are responsible.

  Referring now specifically to FIG. 8, the present embodiment includes additional options specifically related to the synchronization process described above and available to customer project site management level users. However, as described above, when a URL related to a website in the web application area is input, the home page 800 is displayed to the customer-side project site management user. Again, several options are available at this point for customer project site management users. Prior to logging in to gain access to user-specific asset information, the customer-side project site management user is responsible for help page 802, site map 804 showing the layout of the website, to facilitate communication with the website operator. A plurality of management pages, such as a contact page 806, a feedback form 808 and an associated send page 810, can be selected. From either the home page 800 or the management pages 802 to 810, the customer side project site management user can select to log in to the site. In response to this selection, a customer-side project site management user is provided with a login form 812 for receiving login information such as, for example, a username and password combination. Subsequently, this information is received and processed in the manner outlined above to determine the level of site access provided to the customer side project site management user. If it is determined that the login information is inaccurate, an appropriate error message page 814 that prompts the user to re-enter the information is displayed. Following entry of the appropriate login information, a main menu 816 is displayed to the customer-side project site management user including several options including a synchronization option, a search option by asset number or RFID tag number, and a project selection option. The

  Specifically with respect to synchronization options, the customer side project site management level user is authorized to synchronize asset management information between the website and the remote client computer system in the manner detailed above. In particular, by selecting a synchronization option from the main menu page 816, a synchronization selection form 818 is displayed where information regarding the information to be synchronized is transmitted. This information should include at least the local file location for the XML file described above that is later uploaded to the website. Next, sending the completed form 818 creates an email message 820 confirming the synchronization process.

  Returning to the main menu 816, the customer side project site management user can also select a view of the project or asset specific information in various ways. Initially, the user can simply enter an asset identification number or RFID tag number and choose to view the asset associated with that number. In the preferred embodiment, this number can be entered directly on the main menu 816. This transmission of the number will then display the corresponding asset in customer specific format on page 838. Once the asset search results are displayed, the user then has the ability to accept or reject the asset listed on page 842, the ability to view additional information about the selected asset on page 844, or external on page 840. Has the ability to export search results to a spreadsheet application. Additional information regarding the content of asset receipt page 842 and asset detail page 844 is described in further detail below.

  Returning to the main menu 816, the user can also retrieve asset management information by selecting an available project. When this option is selected, a listing of available projects is displayed on page 846. From this location, the user can view on page 848 project level detailed information including a listing of all assets associated with the selected project and select to search for assets contained within the project on page 850. . Specifically looking at page 848, when project level detailed information is displayed for the selected project, the user has several options available for displaying additional information. Initially, the user can choose to display an asset search page 850 to further narrow the number of available assets. In addition, the user has the option to select a specific asset or collection of assets and view this information in a customer specific format. In addition, from the project details page 848, the user also has the option to view project level forecast information. With respect to prediction information, when this option is selected, a material list prediction page 854 is displayed that includes various prediction information regarding the number of assets associated with the project, the size of the assets, and the like. At this point, a choice to view the asset specific forecast information is provided. When this is selected, an asset prediction page 856 is displayed.

  Returning to the asset search form on page 850 and selecting this page from either the project selection page or the project details page, information about a particular asset or required asset is transmitted. When the asset search form is transmitted on page 850, the resulting asset information is displayed on page 838 in a customer specific format.

  Returning now to page 842 regarding asset receipt / rejection, at this point the user can choose to confirm receipt of the asset on page 860 or enter an acceptance exception. If the asset is to be received without exception, the user will simply indicate receipt and when sent will be returned to the asset search listing page 838. However, if an exception is to be entered, an asset exception annotation page 862 is displayed to the user. At this point, the user enters exception information and transmits this information on page 864. From the asset detail page, the user also has various additional options, asset exceptions can be entered on page 862, asset location information can be modified or updated on page 872, and asset on page 870. Storage maintenance details can be viewed, and asset packing list details information can be viewed on page 874. With respect to the asset location page 870, when this page is displayed, any corrections to asset location are made and transmitted on page 876.

  By utilizing the collection of various interactive web pages described above, the customer side project site management user can easily update and view the appropriate level of asset management information. In addition, these users can also synchronize this data with data maintained on the remote client computer system in the manner detailed above.

  With particular reference to FIG. 9, this embodiment includes additional options specifically related to the functions and options available to the customer side high level management level user. However, as described above, when a URL related to a website in the web application area is input, the home page 900 is displayed to the customer side high-level management user. Again, some options are available at this point to the customer high-level administrative user. Prior to logging in to gain access to user-specific asset information, the customer-side high-level administrative user can facilitate help page 902, site map 904 showing the layout of the website, and website operators. A plurality of management pages, such as a contact page 906, a feedback form 908 and an associated send page 910 can be selected. From either the home page 900 or the management pages 902 to 910, the customer side high level management user can select to log in to the site. In response to this selection, a login form 912 for receiving login information, such as a username and password combination, is provided to the customer-side high-level administrative user. Subsequently, this information is received and processed in the manner outlined above to determine the level of site access given to the customer high-level administrative user. If it is determined that the login information is inaccurate, an appropriate error message page 914 prompting re-input of information is displayed. Following entry of the appropriate login information, a main menu 916 is displayed to the customer high-level administrative user including several options including a search option by asset number or RFID tag number, and a project selection option.

  A customer-side high-level administrative user can select a view of project or asset specific information in various ways. Initially, the user can simply enter an asset identification number or RFID tag number and choose to view the asset associated with that number. In the preferred embodiment, this number can be entered directly on the main menu 916. The transmission of this number then causes page 938 to display the corresponding asset in the customer specific format. Once the asset search results are displayed, the user then has the ability to view additional information about the selected asset on page 944 or export the search results to an external spreadsheet application on page 940. Specifically referring to the asset detail page 944, the user also has various additional options from this point on. In particular, asset storage maintenance details can be viewed on page 970 and asset packing list details information can be viewed on page 974.

  Returning to the main menu 916, the user can also retrieve asset management information by selecting an available project. When this option is selected, a listing of available projects is displayed on page 946. From this position, the user may view on page 948 project level details including a listing of all assets associated with the selected project and select to search for assets contained within the project on page 950. it can. Specifically looking at page 948, when project level detailed information is displayed for the selected project, the user has several options available for displaying additional information. Initially, the user can choose to display an asset search page 950 to further narrow the number of available assets. In addition, the user has the option to select a specific asset or collection of assets and view this information in a customer specific format. In addition, from the project details page 948, the user also has the option to view project level forecast information. For forecast information, when this option is selected, a material list forecast page 954 is displayed that includes various forecast information regarding the number of assets associated with the project, the size of the assets, and the like. At this point also a selection is provided to view the asset specific forecast information. When this is selected, an asset prediction page 956 is displayed.

  Returning to the asset search form on page 950 and selecting this page from either the project selection page or the project details page, information about a particular asset or required asset is transmitted. When the asset search form is sent on page 950, the resulting asset information is displayed in the customer specific format of page 938. From this point on, the asset details page 944 can be selected as described above.

  By utilizing the collection of various interactive web pages described above, the customer side high level management user can easily view the appropriate level of asset management information. Unlike the other user types described above in connection with FIGS. 4-8, the customer high-level administrative user has no access to any website modification or data entry functions, Note that this is because this type of functionality goes beyond both the requirements and privileges of this type of user.

  In accordance with the embodiments described above, the present invention provides a comprehensive system and method for maintaining and accessing asset management information in a manner that is easily implemented and updated. By facilitating both collection and entry of asset management and tracking information and follow-up status and maintenance information, an up-to-date information database can be easily maintained for subsequent review and utility.

  Referring now to FIG. 10, a flow diagram illustrates one embodiment of a handheld device software application and its functionality summarized in FIG. 2 above. As discussed above, the handheld device 226 can be used to perform the same general functions described in FIGS. 3-9 above. In addition, some additional functions such as asset or tag location and search can only be performed by the handheld device.

  Initially, the device user logs into the handheld device at step 1000. For a single user device, this step is omitted, but it should be understood that if additional users are envisaged, step 1000 is used and set equal to the default user. Next, in step 1002, the user selects a project whose information has been downloaded and synchronized (as described above). The general local device database (as shown by element 1003) is limited to either a single project or a small number of projects, depending on the amount of memory contained in the handheld device, but available projects The listing can be extended to include all projects included in the system.

  When a project is selected, the handheld device displays to the user the number of assets in the project as well as a listing of available search / display options. Then, at step 1004, the user can select one of these options to obtain and view information for individual assets or asset management devices. In the illustrated embodiment, available search / display options include asset verification options, automatic scan options, location / view case options, and smart search options. As will be described in detail below, each of these options can be used alone to provide the user with the complete capability to monitor and manage all assets in the project.

  Referring specifically to the asset location / view option, the user selects this option at step 1006 by selecting a particular asset included in the asset drop-down listing associated with the selected project. In response, the handheld device displays an asset information screen, one embodiment of which is shown in FIG. By viewing the asset information screen, the user can easily and quickly determine the current status of the status as well as its approximate location. Particularly with respect to the embodiment shown in FIG. 11, a plurality of indicators 1100 allow for quick access to this information. The indicator is preferably an asset confirmation indicator 1102 that is an indication that receipt of an asset has been confirmed in advance, a tag attachment indicator 1104 that indicates that a particular asset is tagged with an electronic tag, an area scan It includes a tag detection indicator 1106 that is an indication that a tag associated with the asset has been found, and a storage location indicator 1108 that indicates that the selected asset is located at the storage location. Further, additional information for the selected asset can also be viewed by selecting the More button 1110.

  In addition to enabling viewing of asset status information, the asset location / view option allows handheld users to identify specific assets from among several assets that may be grouped together at a storage location or similar location. Assets can be located. Referring to the embodiment shown in FIG. 11, by selecting the locate button 1112, the handheld device searches for available areas of the selected asset. If found, the handheld device will emit a beep or other sound that increases both frequency and volume when the user physically approaches the location of the selected asset. In this way, a handheld device can be used to locate a particular asset in a crowded storage location, protecting the user from manually searching for each available asset.

  Returning now to FIG. 10, the user can also select an automatic scan option from among the various search / display options available. When this option at step 1008 is selected, the handheld device displays an automatic scan screen where the user selects or enters a description of the asset location area, such as “Storage Location” or “Warehouse”. The user then initiates a start scan, which causes the handheld device to scan for asset identification tags within that range. As each tag is detected electronically, the handheld device reads a list of tags displayed to the user. The user then walks around the entire asset location area with the handheld in scan mode.

  When the user finishes scanning this area, the scanning process is stopped so that the handheld device then compares the list of detected tags with the internal database downloaded from the web application. If the handheld device finds a match between the detected tag and the tag in the database, a test is performed to see if the asset has been previously scanned. If the tag has not been previously scanned, the internal database will be updated by “time stamping” the tag with the date and time the tag was detected. Also, if the database record does not have a previously assigned location area, the handheld computer will update the detected tag location with the selected asset location area. However, if the tag is not in the list in the internal database, the internal database list may be in a separate file for later uploading because the identified asset may contain either misassigned or missed shipping materials You can remember this. In this way, the automatic scanning feature generally allows a user to reduce the amount of time previously required to create an inventory table or catalog of asset location areas using such an electronic asset identification device. it can. Since more than one asset can be specified using a single electronic tag, the automatic scan option search results can be provided by the electronic tag number. Once the tag is identified, the user can then select the associated tag number and can view information about the asset associated with the selected tag. One example of an automatic scan result screen is shown in FIG.

  Returning to FIG. 10, the user may select a smart search option at step 1010. By selecting this option, the user can enter various search criteria for a particular asset or group of assets, and can view and / or modify the results retrieved in step 1012. One embodiment of the smart search criteria screen is shown in FIG. 13, which includes PO number, MLI number, and tag number search criteria. Selecting any information in these categories will cause the handheld device to search for assets that meet these conditions. Once the asset is identified, status and location information can be viewed and modified as indicated above.

  If the asset is identified based on specific knowledge or using one of the methods shown above, the user may select a case confirmation option at step 1014 to confirm receipt of the asset, or You can view / modify previous confirmations. When this is selected, the handheld device gives the user the ability to check for receipt of the selected asset for exceptions. Exceptions can be entered at step 1016 and additional exception details can be entered at step 1018. As further indicated above, the above steps can be similarly completed when reviewing or modifying a previous receipt and confirmation of an asset.

  Referring now to FIG. 14, one embodiment of the asset confirmation screen is shown. As shown, the user can indicate whether the asset was received in area 1400 with or without exception. Further, information regarding the asset location can be sent in area 1402, whether the asset has been accepted by the repository can be accepted in area 1404, and the date of the scan can be accepted in area 1406. If further exceptions are entered, an asset exception screen is presented, where the general reason for the exception can be sent, viewed, or modified. In addition, once a general reason is selected, an additional asset exception details page is displayed where details regarding the type and reason of the exception can be entered, viewed, or modified.

  Returning now to FIG. 10, once the asset is verified, at step 1020, information regarding the maintenance requirements or maintenance status of the asset can be transmitted or viewed by user information. In this way, once the requested maintenance task is complete, the user can easily modify the maintenance information for subsequent synchronization and upload it to the asset management database.

  In addition to providing data based on specific search criteria, one embodiment of the present invention also includes total assets received, total assets not received, total assets confirmed, and unidentified It includes a function that limits the number of assets that can be used based on a predefined search condition, such as all assets. By providing this functionality, it becomes easier for the user to drill down directly on the specific asset material being searched.

  By providing the handheld device with the capability to receive and synchronize asset and project information from a centralized database and user field inputs, the present invention better enables accurate and up-to-date exchange of asset management information. Once the asset is located and verified by a user with a handheld device, this information is easily transmitted to the web application area and subsequently made available to various users in the manner described in detail above. By providing the user with the ability to enter information into a remote database on the site with a handheld device, the accuracy of this information is significantly improved.

  Although the embodiments described above meet a number of asset management and tracking needs, the present invention adds dynamic perceptual information storage and storage in addition to the types of static information described in detail above. Additional utilities are provided by including intelligent tracking, asset management and detection devices that enable transmission. Referring now to FIG. 15, a block diagram illustrating one embodiment, such as the intelligent detection device 1500 of the present invention, is shown. In particular, intelligent detection device 1500 includes the following elements: a plurality of connectors 1502 for receiving external inputs, an analog-to-digital converter 1504 for converting received analog signals to digital signals, any of the devices required by the device A processing unit 1506 for performing signal processing, a memory 1508 operably connected to a processor for storing information in the device, a power supply 1510 for supplying necessary power to the processor and other elements, other devices or Each includes a radio frequency (RF) transceiver 1512 and an antenna 1514 to allow the reader to send and receive information wirelessly, and a visual display 1516 on which the device can visually indicate current status or other information.

  In addition to the elements described above, the intelligent detection device 1500 of the present invention also includes at least one sensor element 1518 and a corresponding actuator element 1520. In the manner described in more detail below, sensor 1518 and actuator 1520 may be configured to provide additional information regarding asset shipment and operational status and history. This information is then processed and stored in memory 1508 for subsequent transmission by RF transceiver 1512. In this way, shipping status and asset status can be more accurately identified and maintained. The intelligent detection device 1500 can be configured to include various types of sensors for monitoring and recording shipping and operational status, some of which are described below, which allows the user to potentially You can also know about adverse or damaging situations, or any other defaults on operational guidelines.

  In one example, the intelligent asset management device may include a collision sensor for maintaining a record of asset collisions. The vibration of the asset can be monitored using the vibration sensor. Next, the asset management device acquires the monitored data, performs vibration pattern analysis, and obtains the asset status more accurately. A speed sensor can be used to monitor the speed of the asset and keep a record of this speed. A force / pressure sensor can be utilized to monitor the pressure applied to the sensor. The device then processes the pressure data to determine the pressure direction and pattern. Tilt sensors can be used to assess shipment and operational compliance of asset tilt guidelines. A tamper sensor can be used to provide asset security and access control functions. A level sensor can be used to monitor the level or height of the material being transported / operated. A weight sensor can be utilized to allow wireless weighing of assets for use by a weighing station. The photosensitive vision sensor can be used to monitor tamper regulation or operating conditions. A GPS (Global Positioning Satellite) sensor can be used to provide real-time geographical positioning information of assets. In addition, chemical sensors can be used to monitor special chemicals or assets that are exposed to conditions such as moisture, smoke, carbon monoxide, and the like. While various sensors have been described above, it should be understood that the present invention is not limited in any way by this detail. Conversely, any suitable sensor can be implemented in accordance with the present invention.

  By providing any combination of the asset management device described above and the above sensor, a more accurate display of asset location or activity / history is available to system users according to the method described in detail above It can be.

  In addition to including various sensors, the processing unit 1506 of the asset management device 1500 can also be configured to include signal processing and decision making (SPDM) functionality. In this manner, information received from the sensor unit can be dynamically processed and stored according to programming choices, rather than raw raw data that must be further processed when received by the reading device. In one embodiment, an asset management device equipped with a speed sensor can be further configured to process the monitored speed so that only information about speeds above a certain threshold is recorded for future searches. . This ability to process received information dynamically greatly improves the flow of relevant information between the asset management device and the end user receiving status information therefrom.

  In addition, for asset management devices that perform a broadcast function (ie, the asset management device communicates information simultaneously without first receiving an explicit request), SPDM processing allows the device to do so only when a particular situation exists. Simultaneous communication can be executed. In this way, a dynamic network of intelligent management devices can be maintained while continuing to maintain sufficient power supply to operate for an extended duration. Conversely, simultaneous simultaneous reporting of information will significantly increase the power needs of each device, thus reducing the overall lifetime of such devices.

  According to one embodiment of the present invention, the asset management device processor can also be configured to allow devices to communicate between devices. By allowing the transceiver unit to share information with other devices as well as the handheld or fixed reader described above, information regarding asset location and status becomes more readily available. In addition, combining this function with SPDM processing further provides a pervasive information science ubiquitous system where information monitored and processed by a single device is similarly positioned to monitor various situations. Can be shared between devices.

  An additional feature of the present invention is an intelligent asset management device with low power requirements, thereby enabling extended operational use. In particular, the power supply 1510 is a passive device that, in one embodiment, transmits information only when queried by a reading device or another asset management device, and only over a short distance, eg, 7 to 8 feet. Alternatively, the asset management device of the present invention can be an active device that actively transmits information in response to a predetermined situation over an extended distance, such as about 200 feet. In these embodiments, the power source is more robust and can include elements such as photovoltaic film (eg, solar film), or other context-sensitive power source. In a photovoltaic embodiment, a power supply with one film can sufficiently power the device for a week without the need for additional light. Other embodiments include a power source driven by wind, pressure, motion, and the like. By supplying other power sources to the conventional battery, the lifetime and range of the asset management device can be further extended.

  Referring now to FIG. 16, one embodiment of a graphical display 1602 of the handheld device 1600 of the present invention is shown. In this embodiment, the intelligent asset management device is configured to include an acceleration sensor that can be used to record changes in acceleration received by the asset management device, and is therefore attached to the asset. Changes in acceleration can indicate asset collision and tilt or rollover. Once the asset is received in the manner described above, the handheld device can request and receive data measured by the accelerometer. As shown in FIG. 16, the graphical display 1602 shows a graph of potential over time, with significant changes in acceleration indicated by large spikes 1604 and 1606 in the graph. These surges probably indicate an impact or tilt on the asset.

  Referring now to FIG. 17, a flow diagram illustrating one embodiment of a method for receiving assets configured to include the intelligent asset management device of FIG. 15 is shown. At step 1700, the asset is received by the carrier for shipment to a final destination. Next, at step 1702, the attached asset management device operates and monitors the shipping process according to the sensors incorporated into the device. As explained above, these sensors can include force sensors, vibration sensors, collision sensors, or the like.

  At step 1704, the asset is received at its destination in the manner shown above in FIG. Next, at step 1706, the recipient reviews the information collected by the asset management device during transit. At step 1708, it is determined whether to accept or reject the asset based on the reviewed information. Once determined, the recipient updates the asset management system at step 1710 with the determination and any other status information regarding the asset.

  Referring now to FIG. 18, a flow diagram illustrating one embodiment of another method for using the intelligent asset management device of FIG. 15 is shown. In this embodiment, the plurality of asset management devices are configured to include a coordinating sensor and a collector for enabling wireless transmission of information between the plurality of management devices. In one embodiment, the system can include at least one rail signal configured to include a single sensor. In step 1800, a signal is activated. Next, at step 1802, the signal sensor device is activated and transmits signal activity and status information such as red, yellow, green, and the like.

  According to the present invention, a locomotive transport asset or individual asset within a locomotive is configured to include an intelligent asset management device having a collector. In step 1804, the locomotive passes through a predetermined neighborhood of the rail signal sensor. In step 1806, the collector receives signal operation and status information transmitted from the signal sensor. This information can then be subsequently reviewed at step 1808 to determine the operational status of the signal light as well as its condition when the locomotive has passed.

  Referring now to FIG. 19, a network diagram illustrating one embodiment of an information network 1900 created by a plurality of asset management devices and readers configured in accordance with the present invention is shown. In particular, the network 1900 includes a plurality of asset management devices 1902 that are associated with a particular operating environment. Such operating environments may include general environments such as at least one manufacturing environment 1904 and at least one shipping / warehouse environment 1906. Furthermore, each of these common environments can also be further subdivided into sub-environments. Referring specifically to the manufacturing environment, such sub-environments can include a part manufacturing environment 1908, a material production station 1910, and a product assembly station 1912.

  Further, each of the environments and sub-environments also includes a station relay 1914 for processing received information between each other and between the various sub-environments and coordinating the relay of signals from the various asset management devices 1902. . In order to facilitate the collection and subsequent distribution of information between essentially different locations, a central network controller 1916 is also provided to further expand the scope of the network 1900. At least one database 1918 is also provided to allow storage and subsequent retrieval of information generated and monitored by various connected asset management devices 1902.

  By providing the intelligent asset management device of the present invention to manufactured products, companies can better monitor the status and status of these assets, thereby making them more satisfied with the end consumer. According to network 1900, information regarding the status of any connected asset can also be easily shared across multiple operating environments. Further, by utilizing an asset management device configured for two-way communication, updated information can be written to the device from both local and remote sources.

  Referring now to FIG. 20, a general flow diagram illustrating another embodiment of the asset management system 2000 of the present invention is shown. In asset management system 2000, an asset management database or collection of databases is provided in step 2002 to maintain a plurality of records relating to various assets to be maintained. In a preferred embodiment, the asset management database includes an Oracle database with records for asset information (TBL-MMAT_CASE), asset update information (TBL-MMAT_CASEUPDATE), and project information (TBL-MMAT_PROJECT). Next, in step 2004, the desktop computer is provided with software for retrieving asset information from the asset management database over a computer network such as the Internet. Preferably, the desktop computer includes an application for downloading asset management information from an asset management database across an application and computer network written in a visual basic (VB) programming language. In one embodiment, this download of asset management information can be scheduled to occur automatically based on a predetermined schedule.

  Upon retrieving the required asset management information from at least one database, in step 2006, a plurality of data files are created or replaced on the desktop computer. In a preferred embodiment, the data file includes a text-based version of asset management information in a delimited format (eg, case.csv or case.xml). A handheld computer is then provided at step 2008 and is typically operatively connected to the desktop computer via a synchronous cradle, docking station, or other hardware-based interface. Alternatively, wireless interfaces such as Bluetooth, IRdA, or 802.11 (x) based systems are also contemplated. Once connected, a plurality of data files are transmitted from the desktop computer to a database on the handheld computer, thereby providing asset information from the asset management database to the handheld computer. In one preferred embodiment, the connection and synchronization between the handheld computer and the desktop computer is performed by Microsoft Corp., named ActiveSync. Achieved through the use of computer applications. The ActiveSync application creates a partnership between the handheld and the desktop computer, allowing subsequent communication and data exchange. In the manner described in detail above, the handheld computer is also equipped with an RFID tag reading function for detecting and exchanging information with the associated RFID tag.

  At step 2010, a software application (eg, TagDetect.exe) held on the handheld computer with the RFID tag reader is utilized to detect both the asset tag as well as the input information about the asset in the manner described above. In the preferred embodiment, the handheld computer software application is written in the C ++ computer language. By using the language, the handheld computer software application generates a data file that includes all asset information updated during use of the application in step 2012. In a preferred embodiment, the data file is a text-based delimited file format such as csv (comma delimited value).

  Next, in step 2014, the handheld computer is re-synchronized with the desktop computer to place the updated asset information data file. In step 2016, this information is then synchronized with the asset management database to maintain the integrity of the underlying asset management database, and the information contained therein is available to all staff who have access to the database. It becomes.

  Referring now to FIG. 21, a flow diagram illustrating one embodiment of a method for creating a handheld database that enables efficient operation that results in processing and power constraints of the handheld computer is shown. In traditional database formation for handheld computers running the Windows CE operating system, the database is typically included in the MicroSoft Windows CE package and uses the class CCeDBDatatabe that serves to encapsulate the database in an object store (eg, the main storage element of a handheld computer). It is formed by doing. Using this class, the lines of the input delimited data file are read using the “AddRecord” method. Unfortunately, this process has proven unacceptable if a number of records are inserted. Thus, the following method achieved a dramatic reduction in handheld database creation / update time.

  In step 2100, a class (CCaseDB in this embodiment) is created on the handheld computer, where each line of data read into the handheld database creates an object of the class. This class is derived from the C object class that is part of the Windows CE standard library. Next, at step 2102, another class (in this embodiment, CCaseDBList) is created using the Windows CE template library and configured to contain each instance of the CCaseDB class described above. This class of structures can be defined by:

typedef CTypePtrList <CObList, CcaseDB ^* >CCaseDBList;
Next, at step 2104, when synchronized with the desktop computer system, a plurality of data objects are created with class CCaseDB for each line of data in the input asset management information file. At step 2106, the combined number of CCaseDB object classes is encapsulated within the CCaseDBList class, thereby adding or removing any revision records from previous versions of this class, and creating or creating a handheld computer database. Will be corrected.

Referring to FIG. 22, a flow diagram illustrating one embodiment of a method for filtering data from an asset management database in creating a text-based data file (eg, case.csv or case.xml) is shown. Yes. At step 2200, the desktop device receives instructions from the user regarding one or more projects for which the user has a responsibility or role. Next, at step 2202, a user request to synchronize the desktop computer with the asset management database is received. At step 2204, the asset and asset update tables (MMAT_CASE and MMAT_CASEUPDATE, respectively) are queried for asset information regarding the received project instructions. One example of a database query is shown below, where each database entry includes multiple information from one of two database structures.
SELECT MMAT_CASE. CASEKEY, MMAT_CASEUPDATE. CASENUMBER, MMAT_CASE. PROJECTID,
MMAT_CASEUPDATE. ETAGNUMBER, MMAT_CASEUPDATE. CONFIRMATION DATE,
MMAT_CASEUPDATE. CONFIRMATIONNAME, MMAT_CASEUPDATE. EXCEPTIONREASON,
MMAT_CASEUPDATE. EXCEPTIONCOMMENT,
MMAT_CASE. ACTUALPICKUPDATE,
MMAT_CASE. ACTUALDELIVERYDATE, MMAT_CASE. MLI, MMAT_CASE. DESCRIPTION,
MMAT_CASE. ICN, MMAT_CASEUPDATE. LAYDOWNLOCATION MMAT_CASEUPDATE. EXCEPTIONPRESERVATION,
MMAT_CASEUPDATE. EXCEPTION PACKAGING,
MMAT_CASEUPDATE. EXCEPTIONPACKING,
MMAT_CASEUPDATE. EXCEPTIONMARKINGS, MMAT_CASEUPDATE. EXCEPTIONPACKINGLIST,
MMAT_CASE. PONUMBER, MMAT_CASE. POLINENUMBER, MMAT_CASE. STORAGESTATUS,
MMAT_CASEUPDATE. DATERECEIVED
FROM MMAT_CASE, MMAT_CASEUPDATE
Here, MMAT_CASE. CASEKEY = MMAT_CASEUPDATE. CASEKEY + PROJECTID = 'KENDL'
In the above example, the received project indication is referenced by the variable “PROJECTID”.

  Next, at step 2206, the retrieved asset information is compiled into a text-based data file and sent to the desktop computer over a computer network at step 2208. By limiting the asset management database query to only the projects for which the user is responsible, the overall size of the transmitted data file is maintained at a much larger manageable size, thereby increasing response time and resources. Requirements are reduced.

  Although the foregoing description includes many details and specifications, it should be understood that these are included for illustrative purposes only and should not be construed as limiting the invention. Many modifications may be made to the above-described embodiments, which are intended to include the appended claims and their legal equivalents, without departing from the spirit and scope of the present invention. .

1 is a general block diagram illustrating an asset and material management system configured in accordance with one embodiment of the present invention. The block diagram which shows the 2nd more concrete embodiment of the asset management system of this invention. 1 is a flow diagram that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information over a computer network such as the Internet. FIG. FIG. 2 is a flow diagram that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information over a computer network, such as the Internet, specifically configured for website management level staff. FIG. 3 is a flow diagram that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information over a computer network, particularly with respect to project site material handling staff. 1 is a flow diagram that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information over a computer network, particularly with respect to exception resolution staff on a supplier side. FIG. 3 is a flow diagram that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information over a computer network, particularly with respect to supplier side project team staff. FIG. 3 is a flow diagram that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information over a computer network, particularly with respect to customer side project site management staff. FIG. 2 is a flow diagram that schematically illustrates one embodiment of a general method for sharing and accessing asset tracking information in a computer network, particularly with respect to customer-side high-level management staff. 1 is a flow diagram that schematically illustrates one embodiment of a handheld device application for use with the present invention. FIG. One embodiment of a handheld device asset information screen. One embodiment of a handheld device automatic scan results screen. One embodiment of a handheld device smart search criteria screen. One embodiment of a handheld device asset confirmation screen. 1 is a block diagram illustrating one embodiment of an intelligent asset management device. FIG. One embodiment of a display screen of a handheld device configured to display sensor information received from an intelligent asset management device. FIG. 11 is a flow diagram illustrating one embodiment of a method for receiving assets configured to include the intelligent asset management device of FIG. FIG. 11 is a flow diagram illustrating one embodiment of another method for utilizing the intelligent asset management device of FIG. 1 is a network diagram illustrating one embodiment of an information network created by a plurality of asset management devices and readers configured in accordance with the present invention. The general block diagram which shows another embodiment of an asset management system. 1 is a flow diagram illustrating one embodiment of a method for creating a handheld computer database. FIG. 3 is a flow diagram illustrating one embodiment of a method for filtering data from an asset management database.

Explanation of symbols

100 Asset and Material Management System 102 Asset Management Server Computer System 104 Remote Client Computer System 106 Query Device

Claims (20)

A system that enables extended asset management and tracking functions,
A plurality of electronic asset identification devices, each attached to an asset whose location and information are to be managed, and including at least unique identification information about the attached asset;
An asset management server computer system for holding at least one database containing information about the asset identification devices and the assets to which they are attached;
A remote client computer system operably connected to the asset management server computer system for exchanging information over a computer network;
At least one interrogation device operably connected to the remote client computer system;
With
The system wherein the at least one inquiry device receives information from the plurality of asset identification devices and exchanges the information with the remote client computer system.   The system of claim 1, wherein the plurality of electronic asset management devices includes a radio frequency identification tag.   The system of claim 2, wherein the at least one interrogation device includes a handheld radio frequency identification tag reader.   The asset management server computer system further includes at least one web application server computer system for operating a plurality of interactive web pages for the asset identification device and the asset to which they are attached. The system according to 1. The plurality of interactive web pages are:
The homepage,
A login page to receive user login information;
A main menu page for displaying to the user a plurality of options for selection by the user to view and / or modify asset management information held on the asset management web server computer system;
A project detail page to display general information about asset management information about the selected project,
An asset search page for receiving an asset search condition from the user, the asset search page enabling the asset management web server computer system to search for asset management information that matches the transmitted search condition by transmission thereof; ,
An asset search result page for displaying the searched asset management information;
An asset detail page for displaying specific asset management information regarding the selected one of the assets displayed on the asset search results page;
The system according to claim 4, comprising:   The at least one inquiry device further includes a resident computer software application, the computer software application incorporating one or more instructions for wirelessly identifying the presence of a plurality of electronic asset identification devices. The system of claim 1, characterized in that: The computer software application further includes
One or more instructions for receiving a description of the asset location area;
One or more instructions for scanning the asset location area to identify the presence of an electronic asset identification device;
One or more instructions for determining whether the identified electronic asset identification device corresponds to information received from the asset management server computer system;
The system of claim 6 further comprising: A system that enables extended asset management and tracking functions,
A plurality of electronic asset identification devices, each attached to an asset whose location and information are to be managed, and including at least unique identification information about the attached asset;
An asset management server computer system for holding at least one asset management database containing information about the asset identification devices and the assets to which they are attached;
A remote client computer system operably connected to the asset management server computer system for exchanging information over a computer network;
At least one handheld computer operably connected to the remote client computer system;
With
The handheld computer system is operative to exchange information with the plurality of asset identification devices and the remote client computer system, the handheld computer system between the remote client computer system and the plurality of asset identification devices. A system characterized in that it maintains at least one handheld computer database containing information exchanged in   9. The system of claim 8, wherein the plurality of electronic asset management devices includes a radio frequency identification tag and the at least one handheld computer includes a radio frequency identification tag reader.   9. The system of claim 8, further comprising at least one legacy database system operably connected to the asset management server computer system to allow exchange of legacy information regarding assets to be managed. . The at least one asset management database further includes:
A first table for containing asset identification information;
A second table for including an update to the asset identification information;
The system of claim 8 further comprising:   The system of claim 11, wherein the at least one asset management database further includes a third table for containing project information relating to a plurality of assets. The remote client computer system includes:
The system of claim 8, comprising a computer software application that incorporates one or more instructions for receiving asset management information from at least one asset management database on the asset management server computer system.   The computer software application includes one or more instructions for receiving asset management information from the at least one asset management database on the asset management server computer system according to a predetermined schedule. 13. The system according to 13.   9. The system of claim 8, wherein the handheld computer includes software instructions for reading data from the remote client computer system into the handheld database. The handheld computer software instructions further include:
One or more instructions for creating a first class structure for containing individual handheld database entries for a plurality of assets;
One or more instructions for creating a second class structure to provide a repository for each of the handheld database entries held by the first class structure;
One or more instructions for receiving a request to synchronize asset management data with the remote client computer system;
One or more instructions for receiving a data file from the remote client computer system;
One or more instructions for reading a row of data from a data file for each particular asset into an object created in the first class structure during an exchange of information with the remote client computer system; ,
The system of claim 15, further comprising: At least one sensor element;
A processing unit operatively connected to the sensor element and including at least recording, storage, and transmission processing functions;
A power supply operably connected to the processing unit;
A memory operatively connected to the processing unit and the power source;
A radio frequency transceiver operatively connected to the processing unit and the power source;
An antenna operably connected to the radio frequency transceiver and the power source;
Intelligent detection device comprising.   The intelligent detection device of claim 1, wherein the at least one sensor element includes a sensor for monitoring and recording shipping and operating conditions. A method for receiving assets,
Receiving at least one asset at a carrier including at least one intelligent asset management and detection device;
Monitoring the shipping status of the at least one asset in transit to a destination by the at least one intelligent asset management and detection device;
Arriving at the destination;
Retrieving shipment records relating to monitored shipment status of the at least one asset from the at least one intelligent asset management and detection device;
Determining whether the at least one asset is accepted or rejected based on the shipment record;
Including methods.   The method of claim 19, wherein the at least one intelligent asset management and detection device includes at least one detection element for measuring environmental conditions during shipping.