WO1998027505A9

WO1998027505A9 - Method for remote viewing of damage and authorization of repairs

Info

Publication number: WO1998027505A9
Application number: PCT/US1997/022186
Authority: WO
Filing date: 1997-12-03
Publication date: 1998-11-05

Abstract

A digital repair authorization system and method includes acquiring digital estimate data and digital images linked to the estimate data and transmitting (54) the data to a control facility (22) for authorization of the estimate. The estimate data and associated images can be viewed by auditors at control center workstations (30). Digital authorizations are generated and transmitted back (64) to the originating entity. The estimate and image data files are stored in a central database (24) for management information and control.

Description

TITLE OF INVENTION Digital Repair Authorization System and Method

BACKGROUND When an item of equipment sustains damage, it is customary for the owner of the equipment to obtain an estimate of how much it will cost to repair the damage and to authorize repairs based on that estimate. However, in many industries, the process of obtaining and authorizing estimates is cumbersome and inefficient, involving a great deal of paperwork. In the marine cargo industry, for example, cargo containers frequently arrive at the depot damaged. When this occurs, a depot estimator will inspect the container and write up a paper estimate of the damage and necessary repair work. The estimate is then faxed to the local representative of the responsible party (e.g., container owner or shipping line operator) for repair authorization. Sometimes the paper estimate is transferred to a data input form — another piece of paper — and then keyed into the depot ' s computer system or some other system (e.g. , Cedex Services) that connects to the responsible parties.

The container owner/operator will typically dispatch a surveyor to make an on-site inspection of the damaged container. The surveyor goes to the depot, usually around three days to three weeks after the estimate is created, to survey the damage. By this time, the container is perhaps buried in a stack of containers at the depot, and the depot has to use its handling equipment to dig it out for the surveyor. This handling expense is typically absorbed by the depot. Eventually, a revised paper estimate is sent by the survey company back to the container owner/operator local representative who must decide whether to authorize the repairs. If the estimate is above the local representative's authorized limit, he must send the paper estimate to headquarters for approval. The container owner/operator' s headquarters, usually located far away from the depot, must now determine whether to authorize potentially costly repairs — based on no more than a fax estimate of the damage and little or no first-hand knowledge of the state of the container, the competence of the surveyor, or validity of the estimate. Furthermore, after the container is repaired, there is no real follow up to ensure that the repairs were performed satisfactorily. As a result, shoddy repair work often slips through, requiring later re-work to correct the problems. At this stage, however, there is usually no mechanism for tracing the party who was responsible for the faulty repair.

This is particularly a problem in the marine cargo container industry because the containers are typically owned by leasing companies who lease them to shippers for use in a particular ocean shipment, with the lessee being responsible for damage occurring during the lease. A container typically goes on lease in one port (e.g., Tokyo or New York) and off lease at the end of the shipment in a destination port in another part of the world (e.g., Syndey or Amsterdam). Subsequently, the container will go on lease in the original destination port to another shipper who will use it in the shipment of goods to another port (e.g., Los Angeles or Lagos) . The container must be inspected at each port when they go on and off lease and any damage found is normally repaired at a local, independently owned depot.

As just described, the present system for authorizing repairs in the marine cargo container industry relies extensively on paper sent between the parties — depots, local agents, surveyors, owner/operator headquarters, etc. This entails a significant communications cost. In addition, the practice of sending a surveyor to inspect the damage entails a significant cost in time and human resources. Furthermore, the parties who must decide whether to authorize repairs often are operating "in the dark" because they lack the kind of information about the damage needed to assess estimates reliably. Moreover, there is no mechanism for capturing repair information in a central place to manage the repair system, minimize repair and administrative costs, and maximize the useful life of the containers. What is needed, therefore, is a system which enables the speedy creation, communication and authorization of damage estimates and the centralized collection of information relating thereto.

It is therefore one object of the present invention to provide a mechanism for creating estimate data in a form that can be instantaneously communicated to and from an authorizing party situated at a distance from the damaged object. It is another object of the invention to provide a means for authorizing parties to authorize repairs reliably without having to send a surveyor to inspect the damaged object. It is an additional object of the invention to provide authorizing parties with all of the information, including pictorial information, they need to make reliable decisions whether to authorize repairs. It is a further object of the invention to provide a means for recording authorization transactions automatically in a central database for management information and control . It is yet a further object of the invention to provide an efficient mechanism for verifying the quality of repairs having the same advantages just mentioned.

SUMMARY OF INVENTION The foregoing and other objects are accomplished in accordance with the present invention by a digital repair authorization system and method in which all of the data necessary to authorize a repair estimate, including high- quality images of the object of interest, are acquired, stored, transmitted and manipulated digitally. In this way, a repair estimate can be communicated immediately to, and assessed reliably by, an auditor located thousands of miles from the site of the object, thereby eliminating the costly and inefficient practice of dispatching a surveyor to the location of the object for an on-site physical inspection. A digital repair authorization transaction is carried out in accordance with the invention by first generating a digital data file of the estimate, including a unit number identifying the damaged object and an indication of the nature and extent of the repair work required. Preferably, the estimate data file is acquired at the depot by an estimator who enters the data into a mobile data terminal, such as a hand-held computer, during the estimator's inspection of the object. A high-quality digitized image or set of images of the object is also acquired during the inspection using a digital camera operated by the estimator. The mobile data terminal and digital imager are preferably equipped with synchronized, internal clocks that electronically stamp their respective data files with the dates and times at which the data are acquired. Advantageously, the mobile data terminal and digital camera may be incorporated in a single, purpose built device that combines the hand-held computer and digital camera. After acquisition, the estimate data and image data files are uploaded to a local computer at the repair depot for intermediate data processing. Such data processing can include correlating all of the data (i.e., text and image data) corresponding to a given object using the estimate and image data time stamps and creating data file identifiers inserted into each file that link the estimate data and image data associated with a given object.

The data is next uploaded electronically to a database at a control center for authorization of the repair. The control center can be located virtually anywhere in the world; all that is needed is a suitable data link connecting the depot with the control facility. The control facility is equipped with auditor workstations for accessing the estimate database. The high-quality digital images available to the auditors allow them to make reliable judgments about repair estimates without having to make a physical inspection of the object. The time stamps attached to the estimate data and image data files correlate the data and permit the simultaneous display of images with the textual information about the estimate. An electronic authorization is returned to a requesting depot by placing an authorization message, typically within a day of receiving the request, in the depot's electronic mail box at the control center. Authorizations are retrieved by the depot periodically and authorized repairs made accordingly. Post- repair digital images of the object are transmitted back to the control center for storage in the estimate database together with the associated object's estimate and image data files. Thus, a complete digital record of an authorization transaction, including images of the repair work, is preserved so that comprehensive management information reports can be prepared for customers.

Alternatively, in accordance with the invention, the hand-held computer ("Remote CPU") and digital camera can be used to record and create a permanent pictorial and data record of the condition of an object at a specific place and time which record is uploaded to the central database to facilitate later determination of responsibility for damage. For example, cargo containers are often interchanged between different users. The method can document the condition of the container at the point of interchange. When the container is eventually repaired after one or more interchanges, the database can be used to determine which user should pay for which repair line item.

This method can also be used to document the condition of damaged cargo (e.g., household goods shipments) for later resolution of damage claims.

In effect, this separates the data capture, transmission and storage steps from the audit process, which can take place at some later time.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a functional overview of the invention; Fig. 2 illustrates a preferred architecture for implementing the invention;

Fig. 3 is a flowchart illustrating the digital estimate authorization processes of the invention; and Fig. 4 is a flowchart illustrating the repair verification processes of the invention.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT Fig. 1 is a high-level conceptual overview of the functions carried out in accordance with the present invention. All of the processes shown, including acquiring estimate and image data associated with an object 10, transmitting the data to the Control Center 22 and returning an authorization, are carried out in the digital domain. Referring now to Fig. 2, there is shown a preferred hardware platform suitable for implementing the invention. Estimate Data for an object 10, such as a marine cargo container, is entered into a portable Remote CPU 14 running an application program 20 designed to execute the input routines (eg., steps 40, 42, 48, 50 of Fig. 3) described below. A suitable Remote CPU is a hand-held computer, such as the Apple Newton Message Pad 2000, a mobile, pen-based computer which has storage means for storing data in an ISO-9897 format and is equipped with a serial interface for uploading estimate data to a Depot CPU. The Apple Newton is further equipped with an internal clock for time-stamping the data as it is entered into the computer. The Remote CPU is preferably carried by a resident depot estimator during inspection to facilitate entry of estimate data in real time. The Remote CPU may, alternatively, be a laptop PC or other general purpose computer having suitable input/output, central processing unit, memory and clock means for receiving and storing the estimate data. Digital images of the object 10 are acquired using digital camera 12. One example of a suitable digital camera is the Kodak DC50 digital camera. The Kodak DC50 is equipped with an internal clock that time-stamps the image data files, as well as a PCMCIA card for uploading the digital Image Data to the Depot CPU for merging with the estimate data. It is preferable that the clock in the digital camera be synchronized with the clock in the Remote CPU so that the pictorial data can be properly correlated to the object and estimate data to which they relate. Estimate data and image data could also be uploaded to the Depot CPU via wireline or wireless modem transfer (with the Depot CPU and Remote CPU and digital cameras provisioned with wireline or wireless modem interfaces) . Depot CPU 16 is preferably a desktop PC, such as an Apple Macintosh-compatible PC, having interfaces for sending and receiving data to/from the Remote CPU (e.g., serial interface) and digital camera (e.g., PCMCIA card) and storage means for holding the estimate and image data files. Depot CPU 16 preferably also includes an internal clock, to which the Remote CPU and digital camera clocks are synchronized; i.e., the Depot CPU clock can be used as the synchronization reference for synchronizing the Remote CPU clock with the digital camera clock. It is convenient for the Depot CPU to be located at the repair depot for purposes of periodically uploading the contents of the Remote CPUs and digital cameras by estimators. Preferably, uploading of estimate and image data to the Depot CPU is performed at least once a day. The depot CPU is programmed with application program 18, which instructs the Depot CPU to insert an identifier in the estimate and image data files for each object so as to distinguish the data sets for each object from data collected from other Remote CPUs and digital cameras at that same depot. Application program 18 further instructs the Depot CPU 16 to upload periodically the estimate and image data to Control Center 22. Of course, a depot can be furnished with any number of Remote CPUs and digital cameras, depending on need. And, it is contemplated that a multiplicity of Depot CPUs, in different repair depots and ports, would, in practice, be linked to the Control Center 22. For simplicity of illustration, a preferred embodiment will be described with reference to a single Remote CPU 14 , digital camera 12 and Depot CPU 16.

Data transfer between the Depot CPU and the Control Center 22 is accomplished via a data link 21, such as an asynchronous connection over an X.25 packet switching network, Internet connection, dedicated high-speed data line, or modem connection over a dial-up public-switched network telephone line. Off-the-shelf communications interfaces for the chosen data link are provided at the Depot CPU 16 and Control Center 22.

The Control Center 22 preferably includes an application server 26 programmed with an application program 28 to execute the processes of the invention in conjunction with suitable commercially-available database management software loaded on database server 24. Alternatively, some or all of the functions of the application server could be located in each auditor workstation 30, programmed accordingly. A suitable application server 26 is the SUN Sparc-Server workstation. Application program 28 utilizes an application generator such a ORACLE FORMS to build a user interface suitable for entering and displaying the data that is processed in accordance with the present invention. ORACLE FORMS also contains database access tools that facilitate interactions with the database server 24. Another suitable database software package is Cinebase, an object-oriented database program which is particularly useful for applications involving large quantities of data, such as the storage and manipulation of digitized images like those created with the present invention. Database server 24 also functions as a mail server for the depots and customers linked to the Control Center. Electronic mail functionality is provided by commercially- available e-mail software. Workstations 30 are provided at the Control Center 22 for use by the "remote" repair estimate auditors. These auditor workstations need not be physically located at the Control Center, however; in fact, such auditor workstations could be located anywhere in the world, with connections to the Control Center 22 provided by data links of the type described above. The auditor workstations could be general purpose computers running off-the-shelf terminal emulation software, such as CROSSTALK, for interacting with the application and database servers at the control center. If a database software package such as ORACLE FORMS is being run at the control center, the auditor workstations would also be equipped with standard VGA graphics cards and XVT graphics software to display the graphical user interface presented to the auditors. Auditor workstations 30 are also equipped with display hardware and software to display the high-quality digital images, such as for example, those produced by the Kodak DC50 or other digital cameras. In one embodiment, the application program 28 running on the application server 26 executes routines that merge the display of the digital image data with the corresponding text estimate data in an ISO-9897 format.

Alternatively, application program 28 (and application server 26) may be replaced by SUN SPARC stations at each auditor workstation running an application program designed to facilitate interaction of such workstations with database server 24 and to display the text, graphics and image data associate with an estimate.

The application server (if used) , database server and auditor workstations may be linked via well-known local area networking or equivalent techniques (such as those used to construct "intranets") .

Customers (e.g., cargo shipping line, cargo container leasing company) , to whom requests for repair authorizations may be referred from time to time (as described at below) , may be connected to the Control Center 22 via data links (such as those described above) , with off-the-shelf communications interfaces on either end.

Although the architecture of the present invention has just been described with reference to a particular configuration of hardware/software elements, those skilled in the art to which the present invention pertains will understand that many other equivalent hardware/software configurations are possible for carrying out the system and processes described herein, and such other suitable platforms are intended to come within the scope of the present invention.

Attention will now be focussed on how the elements shown in Fig. 2 cooperate to implement a preferred embodiment of present invention, using the example of a damaged cargo container in need of repair. The coding of application programs 18, 20, and 28 to execute the routines described below will be readily apparent to the ordinarily-skilled computer programmer. Estimate and Image Data Capture Turning now to Fig. 3, a diagram is shown which traces the flow of data in the present invention from data capture through to repair authorization. The process begins with the entry of estimate data into the Remote CPU (Apple Newton in the preferred embodiment) by the estimator during his inspection of the container. It is noted at the outset that any number of conventional methods may be employed for entering data items into the Remote CPU 14. Preferably, the estimator is presented with a screen display or series of screen displays, generated by application program 20 running on the Remote CPU, in which each data item to be entered has a defined field identified on the display(s) . Data items can then be entered using a standard PC keyboard, if, for example, a laptop is used as the Remote CPU. Alternatively, and preferably, the Remote CPU is a pen-based computer, such as the Apple Newton or similar, wherein the data items are entered simply by tapping menus of choices or diagrammatic representations of the container on a screen display. If an Apple Newton is used, alphanumeric data is entered via the pop-up keyboard for alpha characters and the "numberflipper" for numerical data.

In entry routine 40, the estimator opens an estimate data file and enters certain basic information that uniquely identifies the estimate and sets the parameters for the estimate session; information such as a 1) port and depot code, 2) record number (estimate serial number) , 3) currency code, 4) labor rate, 5) dimension codes (i.e., units of measurement - e.g., cm, inches, feet), and 6) estimator name may be entered at this stage of the routine. The estimate serial number is preferably automatically generated by the Remote CPU, with the port and depot codes composing the first characters of the serial number so as to readily identify the estimate with the site where it was generated, as well as to distinguish the estimate from those generated at other ports and depots. If the particular depot where the estimate is being generated supports more than one Remote CPU, care must be taken that estimate serial numbers do not overlap. This can be accomplished, for example, by generating at the Depot CPU a list of estimate serial numbers that is exclusive to each Remote CPU at the depot and downloading this list into each Remote CPU's memory. The other data items entered in this step of data entry routine 40 are preferably hard-coded into the Remote CPU and loaded automatically at set-up. The Remote CPU electronically stamps, using the unit's internal clock, the estimate data file with the time and date at which it is created by the estimator. Optionally, entry routine 40 can be preceded by the acquisition of a series of digital images of the container by the estimator, including a close-up image of the container's identification plate showing the container specifications and date of manufacture. As noted above, the digital camera 12 used to acquire such images time-stamps each digital image based on the camera's internal clock, which is synchronized to the Remote CPU 14 clock, thus providing a means for correlating the images with the estimate. The images acquired at this stage of the estimate include, preferably, full views of each face of the container whether or not damaged or in need of maintenance. This creates a digital record of the condition of the container on a given date and time, which is quite useful in tracing where and when subsequent damage occurs.

Next in estimate data entry routine 40, data associated specifically with the damaged object under inspection (in this example, a cargo container) is entered into the Remote CPU 14. The information entered into the Remote CPU in this step should be sufficient to identify the particular cargo container (or other object being inspected) so that its origins and movements can be traced. This will facilitate, for example, tracking down where the damage to the container occurred. Preferably, the information entered at this stage includes certain information about the container's construction that will aid an auditor at the Control Center 22 in assessing the estimate. Thus, the information entered in this stage of the estimate data entry routine preferably should include:

- an alphanumeric unit (container) number unit type (choice of several) equipment type unit material type (e.g., steel) - equipment operator code transaction type (e.g., offhire, leased- inservice or owned) onhire date (if offhire) After entry of the basic data setting the parameters of the estimate and identifying the container under inspection, the Remote CPU is ready to receive data relating to the damage to the container and the recommended repairs. The estimator begins line item data entry routine 42 by choosing which face of the container to inspect. Again, this can be done be allowing the estimator to pick from a list. For each face of the container, there is an associated data field that indicates whether or not there is damage to that face. If there is/is not damage, the estimator enters an indicator

(such as "yes" or "no") to that effect. Alternatively, there could be two data fields — a "yes" data field and a "no" data field — associated with each face, with the estimator checking the appropriate field. If the estimator enters a positive indication of damage to the face, then line item data routine 42 proceeds to call for the entry of detailed information concerning each item of work indicated on that face. Since the data entered in this step will provide the auditors at the control center with the most important information about the repairs for which authorization is sought, the information should include one or more data fields each corresponding to the type of damage, necessary repair work and estimated number of labor hours to effect the repair. Preferably, the following data items are entered for each line item of work: item number location of damage component code damage code repair code repair quantity horizontal and vertical dimensions of area in need of repair labor hours to complete repair repair material cost responsibility code (to indicate the party who should be billed for the repair or maintenance work)

Data entry using the Apple Newton lends itself to an onscreen graphical depiction of the container which the estimator can tap at the appropriate spot(s) on the display to indicate where the damage is located (for entry of data into the "location of damage" field above) . The estimator could also then tap the appropriate code on a damage code menu for the damage indicated on the diagram. The above data items are entered for each line item of work called for on the chosen face of the container. Each line item of work is electronically stamped with the date and time to facilitate correlation of the line item with a digital image of the line item, which will be described next. The line item is preferably time stamped immediately after entry of the last data item in the line item so that the time stamp of the digital image data file corresponding to the line item data is as close as possible in time.

An important aspect of the invention is the creation of high-quality digital images of the container for each estimate. In conjunction with the entry of data for each line item of work, the estimator uses the digital camera 12 to acquire a close-up digital image of the damage (step 44 in the flowchart of Fig. 3) . The digital camera 12 electronically stamps each image with the date and time to provide a means for associating the image with the line item estimate data just entered. To prevent the estimator from inadvertently skipping the image data acquisition step, line item data entry routine 42 preferably includes a prompt for image acquisition after the line item data is entered. The prompt can include a data field that must be electronically "checked" by the estimator to indicate that the digital images have been acquired before the data for the next line item of work can be entered. Steps 42 through 46 are repeated for each face of the container requiring work. Before completing the estimate, the estimator preferably enters overall container rating and condition codes to provide coarse indicia of the container's state that can be used in the generation of management reports at the control center as described further below. Each estimate data file also contains a status indicator to show whether it is a new estimate for which authorization is requested.

Alternatively, rather than linking specific digital images to individual line items, the link may be to the face of the container (e.g., right side). In such case, the estimate in the Newton is ti e stamped at the start and end of the inspection of that face, and all the pictures with time stamps in this interval are linked to that face. All the image thumbnails for a given face are displayed at the top of the auditor's screen and the damage & repair line items for that face scroll on the screen underneath the thumbnails. After all of the estimate data is acquired, the Remote

CPU 14 prompts the estimator (step 48 of the flowchart in Fig. 3) to re-enter the unit number and equipment type to verify that these data are the same as those entered at the beginning of the estimate session. Any number of estimate data files can be created as described above and stored in the Remote

CPU, the only limitations being the size of the memory in the Remote CPU and digital camera. If desired, a voice recording can also be included with the record in some hand-held computers, such as the Newton.

Data Transfer Next, the estimate and image data is uploaded (step 50) to Depot CPU 16. In practice, the data from the Remote CPU 14 and digital camera 12 are uploaded to the Depot CPU 16 a few times a day using interfaces, such as PCMCIA cards, provided in each unit and serial cables connecting the devices. For security reasons, the data files uploaded to the Depot CPU 16 are preferably not accessible for modification at the Depot CPU, except perhaps for the addition of plain text notes or comments about a particular container.

The upload data step 50 can include preliminary data processing to format or otherwise condition the data files for transmission to the Control Center 22. In one embodiment of the invention, such preliminary data processing includes the generation by application program 18 of an identifier for each estimate data/image data set (a set comprising all of the estimate data and image data for a given object) that is inserted into each estimate and image data file; the identifier digitally link the data set for a given object and distinguishes the data set from data sets acquired by other

Remote CPUs and digital cameras at the same depot (which could bear the same or similar time stamps) . In other embodiments, the Depot CPU 16 can be programmed to search the date/time stamps of data to create digital links between each image and the corresponding line item of work to obviate the need to do this at the Control Center 22 when an auditor requests image data for a particular line item. In still other embodiments of the invention, the Depot CPU might be programmed to merge the estimate and image data files for an object to create a unified alphanumeric/graphical/image data file for the object.

Using communications interfaces at the Depot CPU 16 and Control Center 22, and a data link 21 between the two (see above) , the digital data is transmitted (step 54) to the Control Center 22 for authorization. Such data is also retained in the Depot CPU's memory for later processing. The Control Center application server 26 can be programmed to send a signal to the Depot CPU 16 during off hours to request a data transfer, in response to which the Depot CPU would upload all of the data not yet transferred to the Control Center 22.

Estimate Authorization The Estimate authorization routine 56 of application program 28 will now be described. Data uploaded to the Control Center 22 is stored in the database server 24. All of the data for a given container (linked by their date/time stamps or equivalent digital indicia as described above) is sent to an auditor workstation 30. The auditor is presented with a display of the estimate and image data corresponding to each line item; this is preferably a simultaneous display of text, graphics and image data for each line item generated by application program 28 and suitable cards in each auditor workstation 30. Application programs 31 in each auditor workstation can be designed to search the time stamps of each image data file as the auditor scrolls through the line items such that the correct images are displayed with each line item. Alternatively, the workstations can be programmed to display the data by matching the identifiers generated by the Depot CPU 16 and inserted into each line item/image data set as described above.

For each line item of work on each face of the container, the auditor is provided with a choice — to be entered in a data field(s) associated with the line item data — of approving, deleting (in the case where the auditor deems the item routine wear and tear, for instance) or modifying the estimate. For example, the auditor might determine, based on the image data for a given line item, that the estimator has overestimated the number of hours it will take to perform the work. In that case, the auditor would enter a revised number of hours in an estimate modification data field. Preferably, the auditor is also provided with the capability of marking up the digital images as an aid in explaining the modifications. For example, if a repair line item calls for straightening five dents on the left side of the container and the auditor thinks that two of the dents are routine wear and tear, the auditor can circle those two dents on the image and mark them "w & t", circling the remaining three dents with the note "damage".

The auditor goes through each line item and container face following the same sequence as that used by the estimator in creating the data. The complete revised estimate data file and associated digital images are stored in the database server 24, along with a status indicator (e.g., awaiting audit, awaiting customer authorization, authorized awaiting repair, awaiting post repair acceptance, awaiting post repair re-work, available for use) . The estimate authorization routine 56 also includes calculating the total repair cost for the container based on the labor and materials cost and labor rate contained in the estimate data file as revised by the auditor. In a preferred embodiment of the invention, customers of the digital repair authorization service (container owners/operators) provide the control center with an authorization limit, stored in the control center, against which the revised estimate total is compared in step 58. (The customer associated with the estimate is derived from the data entered into the operator data field by the estimator, as described above.) Estimates above the limit are referred to the customer (step 60 in Fig. 3) by attaching the estimate data file and associated images to an e-mail placed in the customer's mailbox at the Control Center 22. Customers retrieve their e-mail using suitable terminal equipment (i.e., Customer CPUs 32) , and are given the opportunity to review the estimate data and authorize and/or modify the data as auditors do. The Control Center 22 waits for a return authorization e- mail to be sent by the customer before sending authorization to the depot. Estimates that fall below the customer authorization limit are sent to the depot without passing through the customer. It may be desirable to automatically authorize estimates received from reliable depots without the intervention of an auditor. For instance, if the estimate data is associated with a reliable depot (as indicated by the depot data field in the estimate data file) , authorization routine 56 could calculate a total estimate cost before review by an auditor and compare it to a pre-determined authorization limit. If the estimate falls below the limit, the repair work could be authorized automatically, thus eliminating the need to scrutinize the estimate. In step 64, authorizations are returned electronically to the depot in via an e-mail — to which the revised estimate and associated image data are attached — placed in the depot's e-mail box at the Control Center 22. The depot periodically checks its e-mail to retrieve authorizations and associated revised estimate and image data files (application program 18 at the Depot CPU provides this functionality) . It is preferable, for security reasons, to permit the depot to view estimate and image data only from the database server 24. Upon receiving an authorization, the depot arranges for repairs to be carried out in accordance with the modified estimate and image data.

Repair Verification In another significant aspect of the present invention, a repair verification facility is provided for ensuring repairs are performed correctly and for creating a permanent, digitized record of the repair work. Turning now to Fig. 4, the repair verification process is shown in a flowchart format. In step 68, the revised estimate data file (created in the estimate authorization routine 56) is downloaded from the database server to the Depot CPU, which in turn downloads the data file to the Remote CPU, where the original estimate data file is replaced with the revised data. In practice, the Remote CPU will contain estimate data files for multiple containers. Thus, in step 72, the estimator calls up the appropriate revised estimate data file by viewing an on-screen list of unit numbers and selecting the one corresponding to the container of interest. The estimator then examines each line item of work contained in the file in a manner similar to that used to create the original estimate data file (see steps 40-46 in Fig. 3) . As with the creation of the estimate data file, digital images of the repair, linked to the corresponding line item by a synchronized time stamp, are also acquired at this time (step 74) . Next to each line item is a "post repair picture" data field, e.g., a box, to remind the estimator to take a digital picture of the repair. (The Remote CPU could also be programmed not to permit the estimator to go on to the next line item unless the post- repair picture field is populated with data.) Preferably, the estimator checks the post repair picture box immediately prior to taking the digital picture, which time-stamps the corresponding line item close in time to the digital image data files. Next, the revised estimate data file and post-repair digital image files are uploaded (step 76) to the Depot CPU 16, and in turn to the Control Center 22 in the manner described above. However, since the revised estimate data file is already stored in the database server 24, the only data from the estimate data files that need be transmitted are the unit (container) number, record number (estimate serial number) , line item numbers and corresponding time stamps. In this way, bandwidth between the depot and control center is conserved.

Post-repair estimate data files and corresponding digital images are reviewed by auditors at the control center (step 78) in the same way as described in the estimate authorization routine (see step 56 of Fig. ) . The purpose of this step is to ensure the work was performed properly and completely; next to each line item is a data field which is filled in if, in the opinion of the auditor, the work was completed satisfactorily. If, on the other hand, the auditor finds the work on a line item to be have been carried out unacceptably, the auditor indicates this in a re-work data field corresponding to the line item (e.g., a box that gets checked) and marks-up the corresponding digital images to indicate the problem. The line item preferably includes a comment field for the auditor's use in explaining the re-work order where necessary.

If the auditor finds re-work necessary, the Control Center 22 places an e-mail in the Depot's mailbox indicating such, along with the affected line items and corresponding images (step 82) . Steps 40 through 48 of Fig. 3 are then essentially repeated for the affected line items and the data acquired in steps 40, 42 and 44 are retransmitted to the Control Center 22 for approval. The process is repeated as many times as necessary until approval is granted by the control center for all the line items on a given container. Once all repairs have been approved by an auditor, the control center places an approved message in the depot's mailbox on the database server 24 (step 84) . At the same time, the status field of the estimate data file is changed to "available," indicating that the container is ready for hire or reuse. As can be seen from the above description, the all- digital repair authorization system of the present invention provides a highly efficient means for authorizing and monitoring repairs. One of the many advantages of the invention is the permanent maintenance of a digital record of a container's repair history in the Control Center database. This information is extremely valuable for purposes of generating management reports for Control Center customers. The database can also be used to pinpoint the source of faulty repairs that surface later. The "before and after" digital images of the faulty repair provided by the database give container owners/operators the photographic documentation they need to re-bill original repairers for bad jobs. All of this is executed electronically, in the digital domain, with a minimum of human intervention. The database can also be made available on-line to customers to allow them to monitor the performance of depots and auditors, the database essentially becoming a maintenance and repair management information system for customers.

It should be readily apparent that while the present invention has been described in the context of a repair estimate relating to a damaged cargo container, the systems and processes described and claimed herein are readily applicable to the inspection of any object as to which some authorization action must be taken based thereon. For example, any object — "car", "building", "aircraft", "construction equipment" — could be substituted for "container" in the above discussion. Rental car companies in particular should find the invention to be of great benefit for inspecting damaged automobiles since it will permit them to authorize repairs reliably from locations situated great distances from the damage. Insurance companies will also recognize the advantages of the invention for authorizing estimates relating to virtually anything that can be insured. The invention could also be applied to the digital authorization of events, which are intended to be included in the term "object" as used in the foregoing discussion and following claims. Accordingly, the spirit and scope of the invention are not to be limited by the details of the embodiments described above, but rather by the claims that follow.

Claims

What is claimed is:

1. A digital repair authorization method comprising: a) generating a digital estimate data file relating to an object; b) generating a digital image file of the object that is digitally linked to the estimate data file; c) communicating the digital estimate data file and corresponding digital image file to a control center for authorization; d) generating a digital authorization of the estimate at the control center; e) storing the authorized estimate data file and linked digital image file in a central database.