Abstract:
In one embodiment, a system is provided for performing at least one service operation in association with at least one inspected item. The system includes a service data device configured for displaying at least one data screen including at least one checklist configured for operative use in connection with performance of the service operation on the inspected item, the data device being portable and being configured for processing at least one communication; a service administrator having at least one data storage medium configured for storing at least one of the checklists displayed on the data device, the service administrator further having at least one server for enabling at least one communication between the service administrator and the data device; at least a portion of at least one of the checklists being customizable by at least the service administrator; and, at least a portion of at least one of the checklists being electronically interactive in association with performance of the service operation on the inspected item. It is emphasized that this abstract is provided to comply with the rules requiring an abstract that will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. 37 CFR §1.72(b).

Description:
CROSS-REFERENCE TO RELATED APPLICATION/PRIORITY CLAIM 
       [0001]    The present patent application is a continuation of co-pending U.S. patent application Ser. No. 10/666,463, filed on Sep. 19, 2003, which is hereby incorporated by reference into the present application. 
     
    
     BACKGROUND 
       [0002]    In many conventional situations, various non-electronic versions of documents are often used to record, store, track, analyze and/or process data derived from service operations performed on a variety of inspected items. In the context of service operations performed on a machine, for example, such non-electronic documents may be used during periodic machine inspections and maintenance, fluid change procedures, fluid sampling procedures, load bank tests, repair assessments and cost estimates, and other like service operations. Machines and components can lose useful operational life in connection with a number of factors including, for example, failure or inability to plan, prepare, and/or adhere to prescribed maintenance schedules; failure to perform proper tests of fluids employed in machines; ineffectiveness or absence of means for collecting, storing, analyzing and/or processing data associated with equipment operation; poor communication between/among service technicians, distributors, customers and other service providers regarding issues with machine operation; as well as other factors related to inefficient and/or ineffective service operations performed on machines and their components. The inefficiencies attendant upon non-electronic methods, systems and documents often contribute or aggravate the effect of these factors. 
         [0003]    Examples of other contexts in which there is prevalent use of non-electronic documents and processes include the healthcare industry and the financial industry, among others. Manual data entry errors reflect one example of a source of error and potential harm arising from use of non-electronic documents and processes in these industries. In addition, many electronic documentation systems and procedures lack connectivity, and thus do not address lack of communication between/among the various entities associated with service operations performed on inspected items. Furthermore, non-electronic documents are often inflexible in their design, development, and/or application to performance of service operations on inspected items. 
         [0004]    Thus, conventional products and services may benefit from improved methods, systems and products for collecting, storing, analyzing and/or processing data in association with service operations performed on inspected items. Improved communications between/among service administrators, service technicians, distributors, customers and/or other service providers are also needed to enhance the efficiency and effectiveness of service operations performed on inspected items. 
       SUMMARY 
       [0005]    In one embodiment of the present embodiments, a system is provided for performing at least one service operation in association with at least one inspected item. The system includes a service data device configured for displaying at least one data screen including at least one checklist configured for operative use in connection with performance of the service operation on the inspected item, the data device being portable and being configured for processing at least one communication; a service administrator having at least one data storage medium configured for storing at least one of the checklists displayed on the data device, the service administrator further having at least one server for enabling at least one communication between the service administrator and the data device; at least a portion of at least one of the checklists being customizable by at least the service administrator; and, at least a portion of at least one of the checklists being electronically interactive in association with performance of the service operation on the inspected item. 
         [0006]    In another embodiment of the present embodiments, a method is provided for performing at least one service operation in association with at least one inspected item. The method includes displaying at least one data screen on a service data device, including displaying at least one interactive checklist configured for operative use in connection with performance of the service operation on the inspected item, the data device being portable and being configured for processing at least one communication; storing at least one of the checklists displayed on the data device on at least one data storage medium of a service administrator; and, customizing at least a portion of at least one of the checklists with the service administrator. 
         [0007]    In another embodiment of the present embodiments, a computer-readable medium is provided including instructions for performing a method for performing at least one service operation in association with at least one inspected item. The medium includes instructions for displaying at least one data screen on a service data device, including instructions for displaying at least one interactive checklist configured for operative use in connection with performance of the service operation on the inspected item, the data device being portable and being configured for processing at least one communication; instructions for storing at least one of the checklists displayed on the data device on at least one data storage medium of a service administrator; and, instructions for customizing at least a portion of at least one of the checklists with the service administrator. 
         [0008]    In another embodiment of the present embodiments, a label product structured for placement on an object having a radius is provided. The label product includes a data presentation portion including information associated with at least one service operation performed on an inspected item; at least one bar code portion including a bar code having a vertical axis and a horizontal axis; one or more bar code indicia imprinted on the bar code, the bar code indicia being representative of at least a portion of the information associated with the service operation performed on the inspected item; and, the horizontal axis of the bar code being dimensioned as a function of the radius of the object. 
         [0009]    In another embodiment of the present embodiments, a bar code product for use in association with scanning an object having a radius with a bar code scanner is provided. The bar code product includes one or more bar code indicia printed on the bar code product; and, at least one of the bar code indicia having an effective width dimensioned as a function of an arcuate distance of the bar code indicia away from a central axis of the bar code scanner. 
         [0010]    In another embodiment of the present embodiments, a bar code product for use in association with scanning an object having a radius with a bar code scanner is provided. The bar code product includes one or more bar code indicia printed on the bar code product; and, at least one of the bar code indicia having a first thickness and second thickness, the second thickness being greater than the first thickness to provide an effective width dimensioned as a function of an arcuate distance of the bar code indicia away from a central axis of the bar code scanner. 
         [0011]    Other embodiments of the present invention will become apparent to one skilled in the art upon review of the following drawings and detailed description. It is intended that all such additional embodiments be included within this description, be within the scope of the present invention, and be protected by the claims. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0012]      FIG. 1  includes a schematic diagram illustrating various example aspects of the present embodiments; 
           [0013]      FIG. 2  includes a process flow diagram illustrating various example aspects of the present embodiments; 
           [0014]      FIG. 3  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0015]      FIG. 4  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0016]      FIG. 5  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0017]      FIG. 6  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0018]      FIG. 7  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0019]      FIG. 8  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0020]      FIG. 9  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0021]      FIG. 10  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0022]      FIG. 11  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0023]      FIG. 12  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0024]      FIGS. 13A-13B  include an example tabulation of data processed in association with one or more aspects of the present embodiments; 
           [0025]      FIG. 14  includes an example data screen and schematic samples of labels provided in association with one or more aspects of the present embodiments; 
           [0026]      FIG. 15  includes various schematic diagrams provided in association with one or more aspects of the present embodiments; 
           [0027]      FIG. 16  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0028]      FIG. 17  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0029]      FIG. 18  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0030]      FIG. 19  includes example data screens provided in association with one or more aspects of the present embodiments; 
           [0031]      FIG. 20  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0032]      FIG. 21  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0033]      FIG. 22  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0034]      FIG. 23  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0035]      FIG. 24  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0036]      FIG. 25  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0037]      FIG. 26  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0038]      FIG. 27  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0039]      FIG. 28  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0040]      FIG. 29  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0041]      FIG. 30  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0042]      FIG. 31  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0043]      FIG. 32  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0044]      FIG. 33  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0045]      FIG. 34  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0046]      FIG. 35  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0047]      FIG. 36  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0048]      FIG. 37  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0049]      FIG. 38  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0050]      FIG. 39  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0051]      FIG. 40  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0052]      FIG. 41  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0053]      FIG. 42  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0054]      FIG. 43  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0055]      FIG. 44  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0056]      FIG. 45  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0057]      FIG. 46  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0058]      FIG. 47  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0059]      FIG. 48  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0060]      FIG. 49  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0061]      FIG. 50  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0062]      FIG. 51  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0063]      FIG. 52  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0064]      FIG. 53  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0065]      FIG. 54  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0066]      FIG. 55  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0067]      FIG. 56  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0068]      FIG. 57  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0069]      FIG. 58  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0070]      FIG. 59  includes an example data screen provided in association with one or more aspects of the present embodiments; 
           [0071]      FIG. 60  includes a schematic of an example network architecture provided in accordance with one or more aspects of the present embodiments; 
           [0072]      FIG. 61  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0073]      FIG. 62  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0074]      FIGS. 63A-63B  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0075]      FIG. 64  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0076]      FIG. 65  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0077]      FIGS. 66A-66C  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0078]      FIG. 67  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0079]      FIG. 68  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0080]      FIG. 69  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0081]      FIG. 70  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0082]      FIG. 71  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0083]      FIG. 72  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0084]      FIG. 73  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0085]      FIG. 74  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0086]      FIG. 75  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0087]      FIGS. 76A-76B  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0088]      FIG. 77  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0089]      FIG. 78  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0090]      FIG. 79  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0091]      FIGS. 80A-80B  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0092]      FIGS. 81A-81B  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0093]      FIG. 82  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0094]      FIGS. 83A-83B  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0095]      FIG. 84  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0096]      FIG. 85  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0097]      FIG. 86  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0098]      FIG. 87  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0099]      FIGS. 88A-88B  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0100]      FIG. 89  includes an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0101]      FIGS. 90A-90B  include an example network site page provided in accordance with one or more aspects of the present embodiments; 
           [0102]      FIGS. 91A-90B  include an example network site page provided in accordance with one or more aspects of the present embodiments; and, 
           [0103]      FIGS. 92A-92B  include an example network site page provided in accordance with one or more aspects of the present embodiments. 
       
    
    
     DESCRIPTION 
       [0104]    As applied herein, an “inspected item” includes any equipment, document, product, article of manufacture, inanimate object, animate object (e.g., people, animals, and/or other living organisms), and/or any other item suitable for use in accordance with one or more aspects of the present embodiments. In one example aspect, the inspected item can include, without limitation, a “machine” suitable for application to one or more aspects of the present embodiments. Examples of “machines” as applied herein can include, for example and without limitation, a lubrication system, engines, diesel engines, large-scale diesel engines, motors, rotating equipment, generators, emergency machines, emergency generators, compressors, earth-moving equipment, excavation equipment electrical power generation equipment (“EPG” or “EPGs”), equipment that includes a machine (e.g., such as mining equipment, construction equipment, marine equipment, and the like), and/or other like equipment and/or equipment components. It can be appreciated, however, that the scope of the present embodiments may encompass other types of inspected items such as financial documents (e.g., including loan processing in association with the financial documents), patients (e.g., including examination of patients at a health care facility). In addition, it can be appreciated that various aspects of the present embodiments may be readily adapted/configured/structured for applicability to a wide variety and plurality of different inspected items. 
         [0105]    As applied herein, the terms “service operation” and “service operations” include, for example and without limitation, any function, method, process and/or other like activity performed in association with an inspected item. In the context of an inspected item which includes a machine, for example, service operations performed can include, for example and without limitation, maintenance, installation, repair, replacement, overhaul, inspection, fluid changes, and/or any other similar operations, functions and/or activities performed in association with one or more of the machines. In another aspect, in the context of an inspected item which includes a financial document, for example, service operations performed can include, without limitation, data entry, application processing, document storage and retrieval, document transmission, and/or any other similar operations, functions and/or activities performed in association with one or more of the financial documents. In another aspect, in the context of an inspected item which includes a patient, for example, service operations performed can include, without limitation, physical examination, administration of medicine to the patient, receiving/storing/analyzing/processing patient data, health care facility admitting procedures, collection of patient fluids (e.g, blood), and/or any other similar operations, functions and/or activities performed in association with one or more patients. 
         [0106]    As applied to various data device embodiments described herein, the term “interactive” includes the capacity for a user to manipulate data, data fields including data entry fields, buttons, radio buttons, and/or other functions available in the various data device embodiments described herein. 
         [0107]    As applied herein to various embodiments, the term “CSA” can be used to refer to one or more aspects of a calendaring and scheduling application and/or may include any method, system, apparatus, device, product and/or computer-readable media embodiment configured for data collection, processing, storage, and/or analysis in accordance with one or more of the present embodiments. 
       Operational Examples 
       [0108]    The following operational examples are intended to illustrate, by way of example, various embodiments and aspects provided in accordance with the present method, system, product, and computer-readable media embodiments. The intention of providing these operational examples is to teach one skilled in the art how to make, use and/or practice various embodiments of the present invention. The intention of providing the operational examples is not, however, to limit the scope of the present embodiments to any particular details or aspects of the operational examples as described herein. 
         [0109]    Where appropriate, to promote convenience of disclosure and clarity of illustration, detailed discussion included for a first operational example may or may not be repeated for a second, third or other operational example. For example, it will be apparent to those skilled in the art that many aspects of the first operational example described herein with respect to service operations for machines (i.e., “Operational Example 1—Machines”) can be readily and analogously applied to their substantially equivalent and/or functionally equivalent aspects in the subsequently described operational examples (i.e., “Operational Example 2—Patients” and “Operational Example 3—Financial Documents”). 
       Operational Example 1 
     Machines 
       [0110]    Referring now to  FIG. 1 , in one example embodiment of the present embodiments, various types of machines  2  can be positioned at a service site  4 . The machines  2  can include, for example and without limitation, one or more types of electrical power generation equipment (“EPGs”)  2 A, one or more varieties of earth-moving equipment  2 B, and/or one or more other machines  2 C for which one or more service operations are to be performed. In one aspect, one or more service data devices  6  can be employed by a service technician, for example, in association with service operations performed on the machines  2  at the service site  4 . Examples of service data devices  6  can include, as shown, a personal digital assistant  6 A (PDA), a laptop  6 B, a pen-based computer system  6 C, and/or a telephone  6 D (such as wireless telephones including cellular phones, for example, or a wireline telephone). In various aspects, a suitable type of data device  6  includes a capacity for portability such as for performing one or more field service operations, for example. In addition, in accordance with various of the present embodiments, a given data device  6  can be structured/configured for performing communications including, for example, real-time wireless communication, communicating with a computer system to synchronize through a cradle or other equivalent apparatus, storing data as a stand alone device and then subsequently communicating the collected data to another location (i.e., store and forward applications), and/or a reasonable combination of these communications, and/or another suitable form of communication. 
         [0111]    One or more local data storage media  8  can be operatively associated with one or more of the service data devices  6  to receive and store data collected during execution of one or more service operations on the machines. In one aspect, at least one of the local data storage media  8  can serve as temporary storage for collected service operation data. In another aspect, such temporarily stored data may serve as a backup source of data in the event of malfunction or failure of the service data device  6 , for example. In another aspect, the local data storage media  8  can include one or more removable data storage media  8 A. In addition, in another example embodiment of the present embodiments, one or more printing devices  10  can be operatively associated with one or more of the service data devices  6 . In one aspect, at least one of the printing devices  10  can be employed to print a label, for example, associated with a service operation performed on one of the machines  2 . In an example aspect, the label or other item printed with the printing device  10  can include indicia associated with data collected during the service operation such as, for example, two-dimensional bar code indicia including data obtained from a fluid change service operation. It can be appreciated that other information displayed on the data device  6  can be printed on one or more of the printing devices  10  such as, for example, a summary report of data obtained from service operations performed on an inspected item. 
         [0112]    In another aspect of the present embodiments, the service data devices  6  can be configured for operative communication with a service administrator  12  through one or more communication media  14 . In various embodiments, the communication media  14  can include one or more wireless networks  14 A, one or more wireline networks, and/or a reasonable combination of one or more of the wireless networks  14 A with one or more of the wireline networks  14 B. The service administrator  12  can include one or more computer systems  16  such as, for example, a web server  16 A configured to host an network site, for example; a data server  16 B configured for receiving, processing and/or directing the storage of data, such as data related to service operations performed on the machines  2  communicated by one or more of the service data devices  6 ; and/or one or more other computer systems  16 C. In one aspect, data processed by the web server  16 A, the data server  16 B, and/or the other computer systems  16 C of the service administrator  12  can be stored in one or more data storage media  18  operatively associated with the computer systems  16  of the service administrator  12 . In one aspect, activation of one of the service data devices  6  can include synchronization of the service data device  6  through the communication media  14  with one or more computer systems  16  of the service administrator  12  to update information displayed or stored on the service data device  6 , for example. In another aspect, one or more communications can be enabled between the data device  6  and the service administrator  12 , for example. 
         [0113]    In further examples of the present embodiments, one or more of a distributor  20 , a customer  22 , and/or a service provider  24  can be operatively configured to communicate with the service administrator  12  such as to obtain, review, and/or analyze data associated with service operations performed on the machines  2 . In one aspect, the distributor  20  can be an entity that maintains a relationship with an original equipment manufacturer (OEM) for the marketing, sale and/or service of one or more of the machines  2  and/or their associated components. In another aspect, the customer  22  can be an entity such as a construction company, for example, employing the machines  2  to perform excavation work at a construction site, for example. In other aspects, one or more other service providers  24 , such as a laboratory facility performing analysis on fluid change/fluid sample data, for example, can be configured to communicate with, and access service operation data from, the service administrator  12 . 
         [0114]    In another aspect, the distributor  20  can be operatively associated with a service cost system  26  that can be configured to provide cost estimates such as for recommended repairs (“RRs”) for one or more of the machines  2 , such as when an inquiries are received from the service data devices  6 , for example, for such cost estimates. In one example configuration, the service cost system  26  includes one or more data servers  26 A operatively associated with one or more cost data storage media  26 B. In one operational aspect, the service data devices  6  can communicate one or more service reports to the service cost system  26  of the distributor  20  to solicit cost estimate information for performing one or more recommended repair, installation, replacement, and/or other maintenance activities for one or more of the machines  2 . 
         [0115]    In various embodiments discussed herein, data input for the service data device  6  can be performed substantially automatically by communication of the service data device  6  with one or more of the computer systems  16  of the service administrator  12 . In other embodiments, data input for the service data device  6  can be conducted partially by manual data entry and/or partially through substantially automatic data retrieval from one or more of the data storage media  18  of the service administrator  12  by means of communication of the service data device  6  with the service administrator  12  through one or more of the communication media  14 . In one example, entering a serial number as a key identifier into a data manipulation screen of the service data device  6  can execute a retrieval program to access, collect and pre-populate the data screen with other data associated with the entered serial number such as, for example, customer name, last service type, last service date, and other data linked to the serial number. In other embodiments, a machine can be equipped with a bar code label that includes data such as a machine serial number, for example. In these embodiments, data entry for the service data device  6  can be performed by scanning the bar code label, RFID tag, or other indicia with a bar code reader, for example, to input data represented by the bar code label into the service data device  6 . 
         [0116]    In various of the present embodiments, the service data device  6  can be programmed/configured to retrieve, display and/or communicate various data manipulation screens, including at least one interactive data screen, in association with collecting, processing, storing and/or analyzing data obtained from one or more service operations performed on one or more of the machines  2 . Referring now to  FIGS. 1 and 2 , one illustrative overview method embodiment is provided in accordance with the present embodiments. In step  202 , the service data device  6  is accessed, such as by a conventional login procedure, for example. In step  204 , the service data device  6  is synchronized with data stored, for example, within one or more data storage media  18  of the service administrator  12 . In one embodiment, synchronization between the data device  6  and the service administrator  12  of step  204  can be structured/configured to occur prior to the login procedure of step  202 . 
         [0117]    In step  206 , one or more service operations can be performed on one or more machines in connection with the function of the service data device  6 . In various example aspects, performing service operations in step  206  can include performing one or more assigned work orders in step  206 A and/or performing one or more unassigned or new tasks in step  206 B. Either or both of steps  206 A and  206 B may involve completing one or more checklists in step  206 C. In addition, in step  206 D and in association with performing one or both of steps  206 A and  206 B, data are input to the service data device  6 . As shown, examples of types of data input in step  206 D can include, without limitation, text entered by keyboard, text entered by use of a pen-based computer system, verbal communications recorded by one or more microphones including one or more microphones configured to eliminate, reduce and/or filter background noise for a recording, verbal communications received and transcribed into text format, digital photograph data and associated annotations, populated data provided through communication of the service data device  6  with the service administrator  12 , for example, and/or other types of suitable data input. In various aspects, one or more types of input data (e.g., text entries) can be stored for subsequent retrieval such that recurring, repetitive service operations (e.g., warranty repairs) can be cataloged to corresponding input data and retrieved/displayed for subsequent service operations. As applied herein, a “repetitive” service operation can include any set of service operations wherein at least one data field, at least one portion of a report, or other data are replicated across multiple service operations. It can be seen that such capability minimizes the need for a service technician, for example, to replicate data entry particularly in the context wherein multiple, at least substantially identical service operations are performed on multiple inspected items. Other service operations performed in step  206  can include performing one or more load bank tests in step  206 E, performing one or more fluid change or fluid sampling operations in step  206 F and generating one or more labels in step  206 G as a result of the processing of step  206 F, and/or calculating a cycle time associated with performance of service operations in step  206 H. In addition, and in view of specific example embodiments described hereinafter, it can be appreciated that other types of service operations can be performed in step  206 I. 
         [0118]    In step  208 , one or more service reports reflecting data collected and processed during performance of the service operations in step  206  can be generated. In step  210 , service reports generated in step  208  can be communicated to an appropriate destination such as to the service administrator  12 , for example, the distributor  20 , the customer  22 , or another service provider  24 , for further processing of data included within the service reports. In another aspect, various portions of various reports (such as reports described herein) can be stored, displayed, and/or edited on the data device  6  prior to establishing communication (e.g., synchronization) between the data device  6  and the service administrator  12 , for example, to transmit data collected during a service operation to the service administrator  12 . In other aspects, various labels, reports, and/or other documents, or portions thereof, described herein can be stored, displayed and/or manipulated entirely in bar code format or another suitable scanner symbology format. 
         [0119]    In one embodiment, a service technician, for example, can access the service data device  6  at the service site  4  to initiate communication with the service administrator  12  through one or more of the communication media  14  using the login screen  302  shown in  FIG. 3 . The service technician logs-in by entering technician identification and a password into the login screen  302 . In one aspect, entry of technician identification information can be performed by scanning an identification badge of the technician, for example, such as by use of a bar code scanning apparatus or system. Once the service administrator  12  verifies that access is authorized for the service technician, a confirmation screen  304  can be displayed on the service data device  6  to confirm successful login for the service technician. As shown in  FIG. 4 , a data screen  402  can be displayed on the service data device  6  to advise that an initial synchronization of the service data device  6  should be performed with one or more of the data storage media  18  of the service administrator  12  to acquire the most currently available service operation information. Once synchronization is completed, a confirmation data screen  404  can be displayed to confirm the number and type of changes, for example, that have occurred since the last time the service technician logged into the service data device  6 . In another aspect, the service data device  6  can be configured to establish communication with the service administrator  12  to perform such synchronization functions on a substantially automated basis upon initial login by a service technician with the service data device  6 . 
         [0120]    Referring now to  FIG. 5 , a data screen can include a “Main” button  452  that permits a user of the data device  6  to display a navigation menu  454  including a variety of optional functions that can be accessed through the data device  6 . In one aspect, a “New Workorder” function  454 A permits a user to navigate to one or more data screens where assigned, unassigned and/or other types of work orders can be processed for a machine by a service technician, for example. In one aspect, by selecting a customer and a machine serial number, for example, information can be pre-populated into the data screens permitting a service technician, for example, to enter machine hours/miles, complete one or more checklists, and/or perform/complete other service operations. An “S.O.S. Labels” function  454 B permits the user to navigate to one or more data screens where labels including a variety of data associated with the machine can be generated and/or printed for service operations (e.g., fluid sampling operations as described above with reference to step  206 F) performed in connection with the machine. A “Service Report” function  454 C permits the user to navigate to one or more data screens associated with generating one or more aspects of reports including information gathered during one or more service operations performed on the machine. A “Load Bank” function  454 D guides the user to one or more data screens that include functionality for performing various aspects of load bank testing such as in connection with an electrical generator, for example. A “CSA Photo” function  454 E permits a user to take a digital photograph or digital image of at least a portion of a machine for which service operations are performed. A “Review W/O” function  454 F permits the user to navigate to one or more data screens wherein a previously completed, or at least partially completed, work order for a machine can be viewed by the user. 
         [0121]    Referring now to  FIG. 6 , in an example embodiment provided in accordance with the present embodiments, the service technician can access a work order data screen  502 , which includes a list of assigned work orders to be completed by the service technician. In one aspect, one or more work orders assigned to the service technician can be sorted and displayed by a scheduled date of service, for example, and accessed by means of a conventional drop-down menu feature  502 A, for example. In other aspects, a “New Unassigned” button  502 B and a “Start Assigned” button  502 C can be provided on the work order data screen  502 . Activating the “New Unassigned” feature provides a data input screen  504  in which, among other functions, the service technician can select a customer name  504 A, a type of equipment  504 B (e.g., “Earth Moving” or “Power Systems”), and/or a serial number  504 C for a machine on which unscheduled or unassigned service operations are to be performed. As shown, data for a given machine can be input to the service data device  6  such as by use of a conventional bar code scanning technology, an RFID technology, or other functionally equivalent and suitable technology. In one aspect, the customer name  504 A, the type of equipment  504 B (e.g., “Earth Moving” or “Power Systems”), and/or the serial number  504 C for a machine can be input by reading a bar code label installed on the machine such as by means of a bar code scanner, for example. Referring now to  FIGS. 6 and 7 , when a “W/O Notes” button  506 D is pressed, the information associated with a given work order is displayed as shown in  FIG. 7 . 
         [0122]    Activating the “Start Assigned” button  502 C, or deciding to “Continue” from the data input screen  504 , displays a data entry screen  506 , which is pre-populated with various data associated with a machine. Among other data that can be selected on the data entry screen  506 , a service type  506 B (e.g., expressed as a number of hours, mileage, and/or other like indicators) can be selected to determine which service operation checklist is to be applied for servicing the machine. Data such as the number of hours/miles shown on an hours meter or odometer operatively associated with the machine, for example, can also be collected/entered into the “Hours Meter” field  506 C portion of the data entry screen  506 . In one aspect, the service data device  6  can compare the hours entered in field  506 C, through communication with the service administrator  12 , to the date/time of a prior inspection or other service operation performed for the machine. For example, if the prior service operation was a 500-hour service performed on a date prior to the current service operation, the service administrator  12  can increment to the next interval of predetermined service operation time due for the machine, such as to a 750-hour service interval, for example. In another aspect of this operational example, given that the 500-hour service has been previously performed, the service data device  6  can confirm through communication with the service administrator  12  that a 750-hour service checklist should be presented in association with service operations to be performed on the machine. In another aspect, the service technician may elect to override the current service interval determined by the service administrator  12  and perform service operations in accordance with a different service interval. It can be appreciated that service intervals for service operations can be configured by the service administrator  12 . It is emphasized that the examples of service intervals applied herein are provided merely for convenience of disclosure. In various aspects, service intervals can be scheduled at varying intervals, with any degree of frequency or non-periodicity, as a function of machine type, environment of machine use, life cycle of machine, and/or other potentially relevant factors. 
         [0123]    Once data input is completed for the data entry screen  506 , a checklist  508 A of activities and/or inspection items for the service technician to perform/inspect can be displayed on the checklist data screen  508 . In various aspects, the checklist  508 A includes a number of predetermined and customized work items that a customer, for example, requires to be performed for a machine. This, the customer can customize the type, content, and/or number of questions/items to be included on the checklist  508 A. In addition, a service technician or other user of the data device  6  who accesses the checklist  508 A may readily edit the checklist by use of drop-down menus and/or data entry fields that are structured/configured to reflect data collected during a service operation on a machine for a given inspection. 
         [0124]    The checklist  508 A can include one or more items such as items  508 B,  508 C,  508 D,  508 E to be inspected during a service operation that includes periodic maintenance, for example. The service technician can select the appropriate entry for each item (e.g., such as “YES”, “NO”, “OK”, or “RR”, among others). In various aspects, entries available for each item can be customizable by the service administrator  12  (as discussed/illustrated hereinafter in more detail). In example aspects, each checklist item can be defaulted to a “NO” or “YES” designation to promote effective completion of all checklist items by the service technician and to allow single-touch toggle of entries (i.e., compare to a first touch to provide a drop-down menu, for example, and then a second touch to make a selection of an entry). In another aspect, the selection of “RR” for a checklist item (such as item  508 B) is interpreted as “Repair Recommended” by the service data device  6 . In various aspects, logic programmed through the service administrator  12  can specify that a given checklist item is applicable on a “less than or equal to” basis with respect to the service interval to which the checklist item is assigned. For example, a checklist item designated for a 1000 service interval and designated on a “less than or equal to” basis is applicable and can be applied to any service operation performed at a service interval equal to or less than the 1000 service interval (e.g., service intervals of 250, 500, 750 and 1000 can be included in one example checklist). In other aspects, entries can include a variety of different types of data fields including, for example and without limitation, calculated fields, manual text entry fields, radio button fields, and/or other types of data fields. 
         [0125]    As shown in  FIG. 8 , the “RR” checklist entry on the data screen  508  can result in association of indicia such as a colored “N” box  508 F, for example, indicating that one or more explanatory notes have been associated with the “RR” checklist item. In various aspects, any checklist item can include an associated note, in addition to annotated “RR” checklist items. A note providing details on the selection of the “RR” designation, for example, can be included on a data entry screen  602 . In other aspects, notes and other data entered by the service technician can be entered/categorized on a “Recommended Repairs” data screen  604 , an “Urgent Repairs” data screen  606 , and/or on an “Other Notes” data screen  608 . In addition, completion of service operations on a given work order can be acknowledged by entering/capturing the signature of one or both of a technician and a customer associated with a particular machine in a data entry screen  610 . In one aspect, any checklist items including items for which repair is recommended (i.e., designated with an “RR”), for example, can be selected and consolidated into a summary portion of a service report generated in association with completion of the checklist items. In another aspect, the service report including the summary of recommended repairs can be communicated to one or more of the distributor  20 , the customer  22 , the service administrator  12 , and/or the other service providers  24  for review, analysis and/or further processing to be conducted pursuant to the issues raised in the service report. 
         [0126]    In other aspects of the various embodiments described herein, a percentage complete status field can be included on various of the data manipulation screen displays associated with checklists processed and completed during field service operations. In one example aspect, for a given checklist, percentage complete can be based on comparing the number of currently uncompleted checklist items to the total number of items included on the checklist. In addition, time/date information associated with initiation of a service operation can be collected, stored, and compared to time/date information associated with completion of the service operation. In various aspects, time/date information can be collected/stored on a per checklist item basis to provide cycle time information for each checklist item as completed by the operation. In other aspects, the sequence in which checklist items are completed by a service technician, for example, can be collected/stored for later analysis to identify an optimum sequence or sequences for completing various service operations. In this manner, cycle times for various service operations can be calculated and employed to compare the cycle time for completion of a service operation performed by a first service technician, for example, to the cycle time for completion of the same service operation by other service technicians. It can be appreciated that such cycle time comparisons can be useful as management/training tools, for example, for improving the performance and effectiveness of service operations. 
         [0127]    In various embodiments herein, data entered into the service data device  6  by a technician, a customer, or another entity or entities providing information associated with service operations can be received/captured into the service data device  6  in a variety of ways. In one aspect, data entry can be performed by use of a keyboard or other similar data input device. In another aspect, data entry can be performed using a pen-based or wand-based data entry system, in which a graphics file including the handwritten note of a technician, for example, is recorded/captured by the data service device  6 . In another aspect, a verbal description of an issue arising from a service operation can be captured and recorded as a voice data file (e.g., through one or more microphones operatively associated with the service data device  6 , wherein the microphone or microphones can be configured for filtering noise to eliminate or reduce background noise that arises during a recording) and/or transcribed into text from the verbal description of the issue by software programmed on the service data device  6  and/or stored in one or more of the local data storage media  8 . In one operational example, a service report generated upon completion of a given maintenance checklist includes an association to one or more voice, text, and/or data files including information gathered during service operations. 
         [0128]    Referring now to  FIG. 9 , once signature data is captured in the data entry screen  610 , a service report screen display  702  can be generated and displayed on the service data device  6 . In various aspects, the service report shown on the screen display  702  includes various data collected and stored during service operations performed using the service data device  6 . In various aspects, any portion of the service report can be communicated through the communication media  14  to one or more of the computer systems  16  of the service administrator  12 . In another aspect, the service report can be remotely printed (e.g., at the remote location of a service site where service operations are performed), such as by use of an appropriate portable printing device  10 . Once work with the service report is completed, the work order screen  502  can be accessed again as shown, such as in the event of a service technician accessing an additional assigned task for which service operations are required, for example. In other aspects of the present embodiments, service reports can be communicated and/or automatically routed to distributors  20 , customers  22 , or other service providers  24  for storage, analysis, and/or further processing of data obtained from service operations. During synchronization with the service administrator  12 , for example, updated service operations data can be communicated to distributors  20  to permit the distributors  20  to act on issues identified in the service report such as by notifying management, sales representatives, and/or service technicians, for example. In one example aspect, the service report including the summary of recommended repairs can be communicated through the communication media  14 , in electronic format or another desired format, to the service cost system  26  of the distributor  20  for generation of cost estimates for resolving issues identified in the service report. Such cost estimates can be further communicated, for example, to the customer  22  for the machine or machines  2 , or components thereof, associated with the service report. 
         [0129]    In another embodiment of the present methods and systems, zone/location information  802 A can be accessed through use of the service data device  6  to display a zone/location screen display  802 , as shown in  FIG. 10 . The zone/location information  802 A can indicate a site where a machine is being employed to perform work, which work site may also be a suitable service site, in one aspect. In addition, the zone/location information  802 A can also be associated with one or more other data fields such as, for example, work order number  802 B, service type  802 C, and/or model/serial number information  802 D. 
         [0130]    Referring now to  FIG. 11 , in another embodiment of the present methods and systems, a service type screen display  902  can be provided. As shown, the service type screen display  902  can include information for a machine such as, for example, work order number  902 A, model number  902 B, serial number  902 C, customer name  902 D, an indication  902 E of the type of machine (e.g., “Electrical”), an hours field  902 F for receiving entry of a current hour meter reading for the machine, a service type (expressed as hours)  902 G representing the number and kind of service operations to be performed for the machine, an indication of the last service type  902 H performed for the machine, and/or a date  902 I of the most recent service operations performed on the machine. In one aspect, a service technician can override the service type  902 G to perform one or more service operations that may be necessary outside usual maintenance schedules. In one example, the service technician can override the service type  902 G to perform service operations that may be missed in the future because of an expected period of operation of the machine without the opportunity to perform service operations during that period of operation. 
         [0131]    In another embodiment of the present methods and systems, one or more labels (such as Scheduled Oil Service (“SOS”) labels, for example) can be generated in connection with one or more fluid change type and/or fluid sampling type service operations. In one aspect, the “SOS Label” button  902 J on the screen display  902  can be activated to display the data entry screen display  1002  (see  FIG. 12 ). In another aspect, the label function can be configured to require data entry for machine hours, for example, before labels may be generated, completed, and/or printed. As shown, the data entry screen display  1002 , and an associated data entry screen display  1004 , include various data options that can be selected/entered by a service technician, for example, in connection with an oil change and/or oil sampling service operation performed on a machine. In various aspects, printed labels can include one or more adhesive surfaces for securement of the label to an appropriate object or machine, for example. In other aspects, printed labels can be provided with one or more non-adhesive surfaces. 
         [0132]    In another aspect, once a machine serial number is entered for a service operation, the service administrator  12  can determine which compartment samples are required and display the required compartments on the data device  6 . It can be appreciated that the particular examples of oil changes/oil sampling are described herein merely for purposes of illustration; it can be further appreciated that other types of fluid change/sampling service operations can be performed in accordance with the present methods and systems. Examples of other fluid change/sampling service operations include, without limitation, transmission fluid, hydraulic fluid, fuels, and other types of fluids employed during operation of a machine. In one aspect, an indication  1002 A of whether or not oil was both changed and sampled at the time of data collection can be entered into the data entry screen display  1002 . It can be seen that information concerning the timing of fluid changes (e.g., a “YES” response entered as the indication  1002 A) such as oil changes, for example, can be communicated to the service administrator  12  to be incorporated into future periodic maintenance schedules, for example, for the machine. In one aspect, intervals such as the time, for example, between “YES” indications  1002 A, for example, can be calculated by the service administrator  12  to determine hour/mileage intervals between service operations for a given compartment, and to determine when another fluid change should be performed for the machine. In addition, because additional types of fluid change/sampling processes are within the scope of the present methods and systems, it can be appreciated that calculations between “YES” indications, for example, can be distinctly performed on a compartment-by-compartment basis. Thus, analysis of the need to perform a transmission fluid change, for example, can be performed in addition to, and independently from, similar calculations performed in association with oil change/sampling service operations. 
         [0133]      FIGS. 13A-13B  display a sample tabulation of stored results obtained, in various aspects of the present embodiments, from various service operations including one or more fluid sampling operations. As shown, data associated with fluid sampling operations can include a serial number of the machine for which service operations are being performed; a compartment identification (e.g., engine, transmission, hydraulic, and others) and can be individually identified on the label, eliminating or reducing the need for a manually-annotated tabulation of checklist items; an amount of oil added, if any, to the compartment; a time/date stamp for the fluid sampling operation; a meter reading for the machine; an “hours on oil” number; a designation of degree of application severity for the machine (e.g., light, medium, heavy, and others); a fluid identifier (e.g., engine oil, transmission oil, hydraulic oil, and others); a fluid viscosity identifier; and/or an “oil changed” indication that records whether or not a fluid change operation has been performed in addition to the fluid sampling operation. Once selections are chosen for a particular machine serial number, or other primary key or identifier, such selections can be configured to become default settings (which can be overridden as described herein) for future fluid operations performed on the same machine to reduce the need for repetitive data entry selections for the future fluid operations. In various aspects, it can be seen that application of various aspects of the present embodiments may increase the available, usable area of a label by incorporating compartment selection into data entry processes on the data device  6  and by including compartment information in association with label generation/printing. 
         [0134]    Referring now to  FIG. 14 , in other aspects of the present embodiments, a label manager screen display  1102  can be provided for managing the generation, completion and printing of labels associated with fluid change/sampling service operations performed on a machine. In one aspect, an icon can be configured to appear on the screen display  1102  once a label has been completed and is ready to be printed, if desired. As shown, an engine related fluid compartment  1102 A can be selected and data associated with oil sampled from the engine can be compiled and generated on a label  1104  or on a label  1106 . In one aspect, a “Print Selected SOS Labels” button  1102 B can be activated on the label manager screen display  1102  to transmit an electronic version of the label  1104  and/or the label  1106  to one or more of the printing devices  10  to generate the label  1104  and/or the label  1106  in a tangible medium such as may be suitable for placement on a bottle, for example, or other container that holds the oil sample associated with the label  1104 . In another aspect, the particular printing device  10  employed to print the label  1104  can be operatively and remotely associated with a laboratory facility, for example, or other service providers  24  that are to conduct analysis of the oil sample. 
         [0135]    In other aspects of the present embodiments, a label including a bar code portion can be pre-printed at a first location and transported for use in connection with one or more service operations at a second location or other locations, such as one or more field service locations, for example. The bar code portion of the label can be pre-populated with various data associated with a machine for which service operations are to be performed. In one example, the label can include pre-populated data such as machine serial number among other machine data. In addition, one or more portions of the label can be configured, for example, for entry of a date, a number of machine hours, a number of miles and/or other pertinent information associated with a service operation. The label can then be affixed, as desired, to a chart, a report, a container, and/or another suitable medium. In another aspect, to resist unauthorized personnel from viewing machine data, the label can include only a bar code portion representing the machine data. It can be seen that printing of labels at a first location permits a service technician, for example, at a second location to benefit from the various embodiments described herein with or without having the capacity to print labels at the second location or other site where service operations such as fluid operations, for example, are performed. 
         [0136]    In other aspects, a label including a bar code portion, for example, can be employed as a means for promoting security of data collected during service operations. In one aspect, data can be stored in the bar code portion for retrieval only by a predetermined and permissible bar code scanning apparatus, system and/or method. Thus, certain data can be stored in the bar code portion of the label that are not visually discernible by a service technician and are configured to be accessible only through an approved bar code scanning apparatus, system and/or method. In other aspects, a label with a bar code portion can be adhered directly to a portion of a machine for which service operations are provided. In this context, the label may serve as a visual reminder of future service operations, for example, to be performed for the machine. In another aspect, one or more labels can be printed on-site with respect to the machine to provide an indication of such future service operations that can be placed on the machine. 
         [0137]    As shown in  FIG. 14 , in other aspects of the present embodiments, the label  1106  can include a data presentation portion  1108  and one or more bar code portions, such as bar code portion  1110  as shown. In one aspect, the bar code portion  1110  includes a bar code  1112  having a vertical axis  1112 A and a horizontal axis  1112 B, wherein the vertical axis  1112 A of the bar code  1112  is structured/configured to be greater in length in comparison to the horizontal axis  1112 B of the bar code  1112  to enhance available, usable area of the label  1106  that can be employed as the data presentation portion  1108 . In various aspects, one or more bar code indicia  1114  are imprinted on the bar code  1112  and may be representative of various information and data associated with a machine, for example, and/or service operations performed on the machine. In various aspects, the horizontal axis  1112 B of the bar code  1112  is structured to be in general parallel alignment with a transverse plane of a variety of objects including, for example and without limitation, machine surfaces, documents, and/or radiused objects such as containers, for example, on which the label  1106 , or at least the bar code portion, is positioned for use. For example, a radiused container  1116  can include at least one transverse plane such as transverse plane  1118 , for example, that can be in general parallel alignment with the horizontal axis of a bar code positioned on a label (e.g., such as label  1106 ) positioned on the container  1116 . In one aspect, the orientation of the horizontal axis  1112 B of the bar code  1112  can be configured in association with a comparatively larger vertical axis  1112 A of the bar code  1112  to derive benefits from enhancing available, usable area in the data presentation portion  1108  of the label  1106  for including and displaying relevant machine data, service operation data, and/or other information. 
         [0138]    It can be appreciated that the bar code  1112  and the bar code indicia  1114  are structured/configured to be read/scanned by a conventional bar code scanning apparatus or system. In various aspects, the length of the horizontal axis  1112 B of the bar code  1112  is dimensioned as a function of a surface area portion of an object to which the label is applied. In the context of an object having a radius, for example, such as a bottle-type container, for example, the length of the horizontal axis portion of the bar code is minimized to a sufficient degree to account for scanning of the bar code and to mitigate the problems attendant upon scanning a radiused object or any object having an arcuate or rounded outside surface area portion. In one aspect, the label  1106  can be die cut or die stamped such as during production of a blank version of the label  1106 , for example, to form a perforation  1122 , for example, or other like structure that permits ready detachment of the bar code portion  1110  from the data presentation portion  1108  of the label  1106 . 
         [0139]    Referring now to  FIG. 15 , in other embodiments of the present embodiments, methods and systems are provided for scanning a bar code  1152  imprinted on a cylindrical object  1154  (such as a bottle type container for fluid samples, for example), generally cylindrical portion of an object, or other arcuate or generally arcuate portion of an object having a radius and/or a circumference. In the example shown, applying a central axis  1156  of a conventional bar code scanner or system (not shown) to the bar code  1152  imprinted on the generally arcuate surface of the container  1154  may result in one or more beams that do not reflect effectively back to the bar code scanner or system after striking bar code indicia imprinted on the bar code. It can be appreciated that such errant beams may provide no results or incorrect results when the bar code on the container is scanned for information. In one embodiment of the present embodiments, at least one bar code indicium  1157  is imprinted along an arcuate portion of the container extending a distance A ( 1158 ) to provide an effective width w e  ( 1160 ) sufficient to permit an effective reading of the bar code indicia  1157  by a bar code scanning apparatus or system. In various aspects, the bar code indicia  1157  can be provided with the enhanced effective width w e  ( 1160 ), in the event that the indicia  1157  are located outside the range of a cone of scanning beams extending from the central axis  1156  of the bar code scanner within an alpha range  1162  of degrees on a first side of the central axis  1156  and/or within a beta range  1164  of degrees on a second side of the central axis  1156 . 
         [0140]    In another embodiment, bar code indicia  1172  are imprinted along an arcuate portion of the container with a first thickness  1174  and a second thickness  1176 . As shown, the thicknesses  1174 , 1176  can be structured to provide a scanning surface  1178  with an effective width w e  ( 1180 ) sufficient to permit an effective reading by a bar code scanning apparatus or system. It can be further appreciated that the difference in magnitude of the thicknesses  1174 ,  1176  can be adjusted to provide a generally flat surface for receiving one or more scanning beams, for example, transmitted from a bar code scanning apparatus or system. 
         [0141]    In other embodiments of the present methods and systems, one or more load bank tests can be performed in connection with use of the service data devices  6  and one or more of the machines  2  which include electrical power generation (EPG) equipment. Referring now to  FIG. 16 , in one example embodiment, a load bank test setup display screen  1202  is shown. The load bank test setup screen is configured to receive data including, for example, a load bank type  1202 A (i.e., whether the machine is a single-phase or three-phase electrical machine), a length of test  1202 B, a testing interval  1202 C, and an option  1202 D to elect an alarm notification in association with the time that each testing interval occurs. It can be appreciated, in accordance with other discussion of customization of checklists presented herein, that one or more data screens associated with load bank testing, or portions thereof, can be customized to address customer requirements. Based on selection of the option  1202 D for an alarm notification, the service data device  6  can generate a notification, such as the dialog box  1204 , at a predetermined time before or after elapse of a testing interval. In one aspect, the data device  6  can be configured to “awaken” automatically when a subsequent load bank test reading is required. In other aspects, the data device  6  can “awaken” from an off state of the data device  6 , or can generate a notification or other prompt in an on-state of the data device  6 , that a subsequent test reading is needed, if the data device  6  is currently powered down or in use for another type of service operation. The dialog box  1204  provides the option for a service technician, for example, to be directed to a load bank test screen display  1302  for single phase testing (see  FIG. 17 ) or to a load bank test screen display  1402  (see  FIG. 18 ) for three-phase testing. As can be seen and appreciated, various data associated with load bank testing can be entered into the load bank test screen displays  1302 , 1402  of the service data device  6  during the test period. In another aspect, upon completion of load bank testing, load bank test results can be displayed such as in the example load test result screen displays  1502 , 1504  shown in  FIG. 19 . In another aspect, load bank test results can be communicated from the service data device  6  through the communication media  14  to one or more computer systems  16  and/or data storage media  18  of the service administrator  12  for storage, analysis, scheduling of service operations, and/or other processing activities. 
         [0142]    In other embodiments of the present methods and systems, a service report module can be programmed within the service data device  6  in which data are collected and stored during one or more service operations performed on a machine. Referring now to  FIG. 20 , a service report data screen  1602  can be provided with various data associated with a machine such as, for example, dealer code  1602 A, work order number  1602 B, customer name  1602 C, model/SN (serial number)  1602 D, equipment location  1602 E, among other data elements as shown. In one aspect of the service report module as shown in  FIG. 21 , an incidents screen display  1702  displays components identified as requiring repair, replacement or other service during service operations performed on the machine. In the example shown, a part number  1702 A, a part name  1702 B associated with the part number  1702 A, and a quantity  1702 C of the part number reflect an incident reported during a service operation by a service technician. As shown in  FIG. 22 , in another aspect of the example, a part number responsible screen display  1802  can be displayed including a description code  1802 A associated with the type of problem presented by the part number (e.g., “G—General Repair”). In addition, data associated with parts/components related to the part number can be displayed in data fields  1802 B, 1802 C, for example. In another aspect, in data field  1802 D, data can be entered by a service technician, for example, providing an indication of whether or not the incident makes the product (e.g., machine) inoperable. In another aspect, a parts screen display  1902  (see  FIG. 23 ) can also be employed to indicate whether parts were left with the customer (data field  1902 A), whether parts were scrapped (data field  1902 B), and/or whether the service operation was completed (data field  1902 C). In addition, if parts are to be returned, a data field  1902 D can be provided for data entry of a return number associated with any returned parts. 
         [0143]    In other aspects of the service report module, one or more screen displays can be provided for data entry of comments and other descriptions of problems identified during one or more service operations performed on a machine. In one aspect shown in  FIG. 24 , a data entry screen  2002  can be provided wherein information associated with a “What did you find wrong:” query can be entered into the service data device  6 . In another aspect shown in  FIG. 25 , a data entry screen  2102  can be provided wherein information associated with a “What was done to repair the problem:” query can be entered into the service data device  6 . In another aspect shown in  FIG. 26 , a data entry screen  2202  can be provided wherein information associated with a “What in your opinion caused the problem:” query can be entered into the service data device  6 . In another aspect shown in  FIG. 27 , a data entry screen  2302  can be provided wherein information associated with a “What were the operational test results:” query can be entered into the service data device  6 . In another aspect shown in  FIG. 28 , a data entry screen  2402  can be provided wherein information associated with “Customer Remarks:” query can be entered into the service data device  6 . As described herein, text can be entered by keyboard, attached as a graphic file (e.g., a .pdf file), entered through graffiti text functions, entered through conversion of voice data, and/or a variety of other types of data entry methods. In another aspect, once entry of service operation related data and remarks is completed, signatures can be captured electronically from one or both of a service technician and a customer, for example, by use of the signature data entry screen  2502  configured for the service report module (see  FIG. 29 ). In other aspects, many of the service report fields can be pre-populated as a part of the service report assignment function. This pre-population of data feature can be beneficial in situations where repetitive service operations are to be performed for multiple machines such as, for example, in the event of warranty repair/replacement required for multiple machines. In various embodiments, and in accordance with prior discussion above, it can be appreciated that data can be entered in the foregoing data entry screens by use of, for example and without limitation, a keyboard, a voice recognition/transcription software, a microphone for recording verbal communications and associated software for storing such communications as voice data files, capture of pen-based data entry in a graphics file, and/or another suitable means for data entry. 
         [0144]    As can be applied to various of the method and system embodiments described hereinabove, the service data device  6  can include a camera, for example, or another operatively associated video apparatus suitable for capturing visual digital data associated with a machine for which service operations are performed. As shown in  FIG. 30 , a photograph data screen  2602  can be used to display a digital image or digital picture of a machine, or portions of a machine, such as portions which are affected by disrepair or other conditions (e.g., corrosion). In one aspect, visual digital data can automatically be made part of the machine inspection or service report, thus obviating the need for a separate attachment or manual download of the visual digital data to create an association with the machine inspection or service report. It can be appreciated that once a digital photograph or digital image of a machine is captured using the service data device  6 , data associated with the picture can be communicated through the communication media  14  to the service administrator  12 . In one aspect, picture or image data can be stored in one or more of the data storage media  18  of the service administrator  12  and manipulated in connection with one or more other service data elements collected, stored and/or processed in association with performance of service operations for the photographed machine. In another aspect, a pen-based system can be operatively associated with the service data device  6  to permit markings, text and other annotations to be added to a digital photograph (as shown) or other image by a service technician, for example, for storage and use in connection with the digital photograph. 
         [0145]    Referring now to  FIGS. 31 and 32 , in another embodiment of the present embodiments, a data screen can be provided that permits a user of the data device  6  to add a new machine for a given customer using the data device  6 . In the example shown, service operations are to be performed for a new earth-moving machine of a given customer. On the data screen, a customer field can be selected and a machine serial number can be specified in a serial number field. In addition, service operations associated with a given service interval can be selected for the new machine by entering a service interval designation in a service interval field. In one aspect, data can be entered or populated into the data device  6  by use of a bar code scan function provided on the data screen. The data screen of  FIG. 32  displays a confirmation function that can be employed to confirm adding the new machine on the data device  6 . 
         [0146]    In another embodiment of the present embodiments, data associated with other new and/or unassigned machines can be recorded by use of the service data device  6 . Referring now to  FIGS. 33 and 34 , data entry screens  2702 , 2802  can be provided for adding one or more EPG machines, such as an engine and a generator, for example, for use by the service data device  6 . The data entry screens  2702 , 2802  can include various data fields such as, for example, a data field  2702 A for entry of an engine serial number, a data field  2802 A for generator make, a data field  2802 B for generator model, among other pertinent data fields associated with specifications and other information for the engine and the generator to be added. 
         [0147]    With reference to  FIGS. 35 and 36 , in other aspects, filter data screens  3002 , 3102  are provided with various data fields, as shown, for entry of data related to, for example, an oil filter, air filter, and a fuel filter. With reference to  FIG. 37 , in another aspect, a component data screen  3202  is provided with various data fields, as shown, for entry of data related to belts, oil and/or coolants, for example. With reference to  FIGS. 38 and 39 , in other aspects, battery data screens  3302 , 3402  are provided with various data fields, as shown, for entry of data related to battery chargers, battery charging, and/or batteries. With reference to  FIG. 40 , in another aspect, a block heater data screen  3502  is provided with various data fields, as shown, for entry of data related to a block heater. With reference to  FIG. 41 , in another aspect, a starter data screen  3602  is provided with various data fields, as shown, for entry of data related to a starter. With reference to  FIG. 42 , in another aspect, a transfer switch data screen  3702  is provided with various data fields, as shown, for entry of data related to a transfer switch. With reference to  FIG. 43 , in another aspect, a miscellaneous data screen  3802  is provided with various data fields, as shown, for entry of data related to other machines, components of machines, or other aspects of machines. In various embodiments, it can be appreciated that data entered into the various data fields of the data screens of  FIGS. 33 through 43  can be accomplished manually, electronically by use of a bar code scanner, for example, and/or remotely communicated from a data source external with respect to the service data device  6 , such as through communication of data received from the service administrator  12 , for example. In addition, in various embodiments, it can be appreciated that data entered into the various data fields of the data screens of  FIGS. 33 through 43  can be used to add a new machine for a given customer, update profile information for a given machine, providing a format for data collection by service technicians, and/or other functions associated with service operations. As shown in  FIG. 44 , in one aspect of the present embodiments, a confirmation message can be displayed confirming that information for the new machine has been added to a memory storage of the data device  6 . 
         [0148]    Referring now to  FIGS. 45 and 46 , in other embodiments of the present embodiments, a data screen can be provided that permits a service technician, for example, to perform one or more service operations associated with an unassigned work order for a given customer. In operation, a customer can be selected in a customer field and a serial number for a machine for which unassigned service operations are to be performed can be selected in a serial number field. As shown in  FIG. 46 , the service technician can proceed to enter an hours number in the hours meter field and/or select a service interval in the service type field, among other data selections such as a work order number, for example, and can then proceed to perform service operations on a previously unassigned work order for the selected machine. In various aspects, banner information can be pre-populated into one or more data fields of the data screens described herein such that, in one example aspect, a service technician need only enter machine hours/miles and a work order number to initiate service operations for an inspected item. In one aspect, unassigned work orders can employ a system of identity ranges to ensure unique identifiers for each work order performed regardless of a work order number entered by a service technician, for example. In another aspect, multiple service operations can be associated with a common work order number, which may be useful for tracking and accounting activities, such as accounting activity associated with warranty service operations, for example. 
         [0149]    Referring now to  FIGS. 47 and 48 , in other embodiments of the present embodiments, examples of data screens that can be used to display and view previously completed work orders are provided.  FIG. 47  illustrates how accessing the “Main” function provides a “Review WO” function, among other provided options.  FIG. 48  displays a list of previously completed work orders in a data display field that can be accessed to facilitate display and/or modification of one or more of the previously completed work orders. 
         [0150]    Referring now to  FIGS. 49 through 57 , example screen displays are provided that illustrate pre-population aspects of the present embodiments. In the context of performing warranty replacement and/or repair work on machines, for example, it can be seen that pre-population of the data screens with conditions expected to be found on a machine for which warranty work may be required can increase the efficiency of service operations performed pursuant to the warranty work.  FIG. 58  illustrates a data screen that can be employed for a customer and a service technician to acknowledge that work has been completed (in accordance with prior discussion hereinabove).  FIG. 59  illustrates a confirmation message that can be displayed once the service report (including data for service operations performed pursuant to warranty work, for example) is completed for the machine. In another aspect, a prompt or other notification can be generated for display in the event that one or more checklist items are not completed, for example, or one or more signatures are not provided, for example. In one aspect, the prompt can be provided as a dialog box notifying a technician of the missing or incomplete information and can be provided with or without navigational functionality to return to the portion or portions of the data screen or screens where the missing or incomplete information should be entered. 
         [0151]    It can be seen that service intervals may be developed and revised based on the data collected and processed through practice of various aspects of the foregoing embodiments. A service interval of 250, for example, and its associated checklist items may be adjusted to a different service interval to account for the practical aspects actual maintenance and repair operations performed on a machine, for example. 
         [0152]    Referring now to  FIGS. 60 and 61 , in other embodiments of the present embodiments, a sample illustration of a network site  3901  operatively associated with the web server of the service administrator is provided. In the example configuration shown, the network site  3901  includes a main page  3902  for obtaining authorized access to the network site  3901 . The network site  3901  also includes an administration module  3904  having one or more operatively associated administration module components  3906 , a customer module  3908  having one or more operatively associated customer module components  3910 , and a CSA module  3912  having one or more operatively associated CSA module components  3914 . An example embodiment of a screen display for the main page  3902  is shown in  FIG. 61 . The main page  3902  can include buttons, for example, that permit a user to access the administration module  3904 , the customer module  3908 , and/or the CSA module  3912 . 
         [0153]    Referring now to  FIG. 62 , an illustrative screen display for a main page  4102  of the administration module  3904  is shown. The administration module main page  4102  includes links to various administrative functions that can be performed on the network site  3901 . As shown in  FIGS. 63A-63B , a user administration page  4202  can be provided to add, remove or edit information associated with various users of the network site  3901 .  FIG. 64  illustrates a division page  4302  including administrative functionality associated with editing one or more division descriptions. In one aspect, division types can include “Earth Moving” and “Power Systems” (or EPG), for example, among other types of potential division designations.  FIG. 65  illustrates a role administration page  4402  that can be employed to configure the roles of various users of the network site  3901 . Examples of roles can include administrator, technician, clerk, among other types of roles.  FIGS. 66A-66C  illustrate a fluid administration page  4502  that can be used to configure data associated with one or more types of fluids such as oil, for example, employed in various service operations for various machines. 
         [0154]    Referring now to  FIG. 67 , a template administration page  4602  is shown which displays various templates that are available, by division, for use on the network site  3901 . In one aspect, a template can form the basis for developing and designing a customized checklist for use in a service operation, for example, which is designed to meet the needs of a particular customer, for example. The page  4602  displays all available templates by division and permits creation and/or deletion of templates to be initiated. In other aspects, template administration functions can be employed in association with customizing one or more data screens associated with one or more load bank testing service operations. 
         [0155]    Referring now to  FIG. 68 , a template detail page can be provided to permit a user to create a new template or edit an existing template. A template can be selected for edit/creation as a function of division type, and an edited/created template can be designated as a default template, as shown. As illustrated in  FIG. 69 , a new template can be given an appropriate designation (e.g., a name) and a “Create” button can be accessed to initiate the template creation process. As shown in  FIG. 70 , one or more inspection types are provided that represent headers for grouping on various reports. The inspection types and their associated checklist questions can be established on a checklist administration page to reflect various questions that a customer needs to have addressed during service operations performed on a machine, for example. In one aspect, the association between inspection types and a given template can be established on a template administration page. 
         [0156]    As shown in  FIG. 71 , once an inspection type is selected, one or more questions associated with that inspection type can be selected for the template. In one aspect, the service interval for a given question may be shown adjacent to the question for convenience of creating the new template. In another aspect, once selection of questions is completed, a “Create Template” button can be selected to finalize creation of the new template.  FIG. 72  illustrates how questions are added to the template during the process of template creation. 
         [0157]    Referring now to  FIG. 73 , a sample template administration page is illustrated. The template administration page displays checklist questions for various inspection types including the service interval associated with each checklist question. 
         [0158]      FIG. 74  illustrates a compartment administration page  4702  which can include information on various fluid compartments such as, for example, oil compartments, transmission fluid compartments, hydraulic fluid compartments, among other types of compartments used in association with machine service operations.  FIG. 75  includes a description code administration page  4802  that can be employed to generate various types of codes used to describe issues associated with machines and/or their components.  FIGS. 76A-76B  illustrate a product family administration page  4902  that can be used to configure various machines, or components of machines, within a particular product family group designation. 
         [0159]    Referring now to  FIG. 77 , an example embodiment of a customer module main page  5002  is shown. The customer module main page  5002  includes information for various customers of machines for which service operations are performed. 
         [0160]      FIG. 78  illustrates a customer detail page  5102  which includes various detailed data associated with one or more of the customers displayed on the customer module main page  5002 . 
         [0161]      FIG. 79  illustrates a contracts page  5202  which includes agreement numbers and customer contacts, for example, for service contracts associated with service operations performed on customer machines. 
         [0162]      FIGS. 80A-80B  illustrate a contract administration page  5302  which includes detailed data relating various machines to contract data such as contact information, length of contract, service area, and other data as shown. 
         [0163]      FIGS. 81A-81B  illustrate an equipment page  5402  which relates customer equipment (such as machines, for example) to data obtained and stored by the service administrator  12  in association with service operations performed on the customer equipment. The equipment page  5402  includes one or more links to data such as, for example, equipment specifications, CSA inspections, service reports, and recommended repairs data. 
         [0164]      FIG. 82  illustrates an equipment detail page  5502  which includes various data fields associated with a particular customer machine. 
         [0165]      FIGS. 83A-83B  are an example of a power systems equipment detail page  5602  provided in connection with a customer machine characterized as a power systems (EPG) machine. 
         [0166]      FIG. 84  illustrates a pictures and audio notes page  5702  that provides, for example, digital photographic images and/or audio recordings association with service operations performed on a customer machine. 
         [0167]      FIG. 85  includes an illustrative load bank test page  5802  that includes information obtained from one or more load bank tests performed on a machine. 
         [0168]      FIG. 86  illustrates an inspection type notes page  5902  including notes recorded by a service technician, for example, derived from service operations performed on a machine. 
         [0169]      FIG. 87  includes a sample inspection checklist item notes page  6002  including notes recorded by a service technician, for example, derived from service operations performed on a machine. 
         [0170]      FIGS. 88A-88B  illustrate a sample service reports page  6102  which includes data collected and communicated from service operations performed on a machine. 
         [0171]      FIG. 89  includes a required repair reports page  6202  that includes checklist items identified with an “RR” designation during one or more service operations performed for a machine. 
         [0172]      FIGS. 90A-90B  include a CSA inspection report page  6302  which illustrates various checklist responses entered by a service technician, for example, performing one or more service operations on a machine. In one aspect, one or more checklist items can be associated with a note or notes entered by a user and stored for subsequent retrieval. As shown, a note or notes can be accessed through one or more hyperlinks, for example, or other links to the data underlying the stored note or notes (hyperlinks are represented as underlined text as shown in  FIGS. 90A-90B ). 
         [0173]    Referring now to  FIGS. 91A-91B , in association with the CSA module  3912 , an embodiment of a create CSA inspection page  6402  is shown. As can be readily appreciated, the create CSA inspection page  6402  permits the service administrator  12 , in conjunction with the customer  22 , to develop a customized approach to performance of service operations for customer machines. Various functions shown on the create CSA inspection page  6402  include designating the type of machine (e.g., “Earth Moving” or “Power Systems”), loading a pre-designed template as a basis for the template being currently developed, adding questions to a checklist for inspection operations, determining service intervals, among other customizable features as shown in  FIGS. 91A-91B . 
         [0174]    In addition, with reference to  FIGS. 92A-92B , a list of assigned inspections can be generated and displayed on an assigned CSA inspection page. Created CSA inspections and their associated service operations can be assigned based on, for example, a technician desired for a particular machine, work order identification, date/time a service operation is required or desired, and/or other factors. In various aspects, one or more assigned CSA inspections can be edited in the event of changes in dates, service intervals, and/or other information changes or updates. 
         [0175]    In other embodiments of the present embodiments, data communicated between the service administrator  12  and the data device  6 , for example, can be communicated in one or more languages such as, for example, and without limitation, English, French, German, Spanish, and/or any other language used for communication between parties. A data screen including a checklist, for example, can be translated using a conventional language translation software, for example, into any suitable language for use on the data device  6  based on the geographical location, culture, and/or preferred language choice, among other factors of the location of service operations. In one aspect, the checklists can be customized such that a given checklist item is provided with a unique identifier (e.g., a numerical identifier) that survives translation of the checklist item into a different language. In this manner, data communicated to the service administrator  12 , for example, as a result of completion of the checklist item (which checklist item may have been completed in a variety of different languages, e.g., different countries, different regions of the world, and so forth), can be filtered based on the unique identifier regardless of the language into which the checklist item was translated and employed in service operations. It can be seen that, in this manner, data from a checklist item can be consolidated in a data storage medium, for example, despite the origin of the checklist data from potentially a diversity of different languages. 
         [0176]    In another aspect, one or more viewing screens can be provided on the data device  6  and/or at the service administrator  12  to permit viewing of a checklist, for example, in a variety of languages. For example, checklists can be communicated to data devices around the world by the service administrator  12  in a non-English language and completed checklists communicated back to the service administrator in English. Functionality can be provided on either the data device  6  and/or the service administrator  12 , in connection with a conventional language translation software, to view translations of checklist items, for example, from one language to at least one other language. In one example aspect, checklists and other data screens can be translated initially into selected multiple languages for subsequent convenience of movement between and among the selected multiple languages. 
       Operational Example 2 
     Patients 
       [0177]    In another operational example, an inspected item can include a patient arriving at a healthcare facility such as a hospital emergency room, for example, to receive medical treatment for a head injury, for example. As noted above, it can be seen that various aspects of the present embodiments applicable to machine service operations described above are equally and analogously applicable to the present operational example. 
         [0178]    In one aspect, a social security number (compare serial number for machines—see above) of a patient can be a key identifier for automatically populating a data screen with information regarding the patient. Data such as patient name, patient address, patient phone number, patient date of birth, sex of the patient, patient next of kin, and other like personal information can be collected on a data screen, stored locally on the data device, communicated to a service administrator operatively associated with the healthcare facility, and/or otherwise processed in accordance with various aspects of the present embodiments described above. In one aspect, once patient data is initially collected and stored, the patient data can be subsequently retrieved and displayed upon entry of the social security number of the patient, for example, or another suitable key identifier. In another aspect, bar code scanning of patient data can occur as the patient is processed through the healthcare facility permitting, for example, patient identity recognition, quality assurance for administered medications, confirmation of proper patient location within healthcare facility, among other functions. In one example aspect, bar code scanning can be employed to reduce the possibility of medication interactions, improper dosaging, patient allergies to medications, and/or the potential for other adverse consequences that may affect the patient. 
         [0179]    Customized checklist questions can be transmitted to a data device employed by a doctor, for example, or other healthcare professional, to inspect or diagnose the condition of the patient. Examples of checklist questions are provided as follows (with various data entry options such as drop-down menu selections, for example, illustrated in parenthesis next to each question as shown, with the process flow assuming that a head injury is selected for the first checklist question): 
         [0180]    Social Security Number: (Enter number) 
         [0181]    Nature of injury (head injury, cut, knee, stomach pain, broken arm, broken leg, ankle sprain) 
         [0182]    How did injury occur? (fall, home injury, sports accident) 
         [0183]    How long have symptoms been present? (Enter data) 
         [0184]    Are you allergic to any medications? (penicillin, aspirin, codeine) 
         [0185]    Is vision blurry? (YES/NO) 
         [0186]    Do you have a headache now? (YES/NO) 
         [0187]    If “YES” where in head is pain? (front, back, side) 
         [0188]    Are headaches a common problem for you? (YES/NO)—How often? (weekly, monthly, yearly) 
         [0189]    Signs of any cuts? (YES/NO) 
         [0190]    Are you sick in stomach, nauseous? (YES/NO) 
         [0191]    Was there any vomiting following the head injury? (YES/NO) 
         [0192]    Did you pass out at any time? (YES/NO) 
         [0193]    When did you last eat? (Select hours ago: 2, 4, 6, 8) 
         [0194]    When was your last X-ray? (Enter date) 
         [0195]    When was your last MRI? (Enter date) 
         [0196]    Are you pregnant? (YES/NO/Not applicable) 
         [0197]    Routing next: (ER, CAT scan, Admit to hospital for further testing/observation, Discharge) 
         [0198]    Medications recommended: (morphine, aspirin, codeine) 
         [0199]    In accordance with aspects and embodiments of the present embodiments described above, a signature of the patient can be captured on the data device such as to ensure informed consent of the patient to receive medical treatment, for example. In addition, the signature of the attending physician, nurse, or other healthcare professional can be captured and stored in association with a service report generated during examination/inspection of the patient as a quality control measure, for example. 
         [0200]    It can be appreciated by those skilled in the art that various aspects of the present embodiments described hereinabove with respect to machines can be functionally and analogously applied to the present operational example within the scope of the present embodiments. 
       Operational Example 3 
     Financial Documents 
       [0201]    In another operational example, an inspected item can include the financial information such as loan application information for a mortgage, for example, for a borrower seeking to procure the mortgage from a financial institution. As noted above, it can be seen that various aspects of the present embodiments applicable to the machine service operations and the patient treatment operations described above are equally and analogously applicable to the present operational example. 
         [0202]    In one aspect, a social security number (compare serial number for machines—see above) of a borrower can be a key identifier for automatically populating a data screen with information regarding the borrower. Data such as borrower name, borrower address, borrower phone number, borrower date of birth, and other like personal information can be collected on a data screen, stored locally on the data device, communicated to a service administrator operatively associated with the financial institution, and/or otherwise processed in accordance with various aspects of the present embodiments described above. In one aspect, once borrower data is initially collected and stored, the borrower data can be subsequently retrieved and displayed upon entry of the social security number of the borrower, for example, or another suitable key identifier. 
         [0203]    Customized checklist questions can be transmitted to a data device employed by a loan officer, for example, or other financial professional, to inspect or evaluate the financial condition of the borrower. Examples of checklist questions are provided as follows (with various data entry options such as drop-down menu selections, for example, illustrated in parenthesis next to each question as shown): 
         [0204]    Social Security Number: (Enter Number) 
         [0205]    Employer: (Enter Employer Name) 
         [0206]    Current position/job: (Enter Data) 
         [0207]    How long have you worked there: (more than two years, less than two years) 
         [0208]    Annual Salary: (Enter Data) 
         [0209]    Other Income: (Enter Data) 
         [0210]    Total Income: (Can be calculated field) 
         [0211]    Provide three credit references: (Enter Data) 
         [0212]    Bank references: (Enter Bank Information) 
         [0213]    Debts: 
         [0214]    Installment loans: (Enter outstanding amount owed) 
         [0215]    Car loan: (Enter outstanding amount owed) 
         [0216]    Credit Cards: (Visa, American Express, MasterCard, Discover) other) 
         [0217]    Other debt: (Enter total outstanding amount owed) 
         [0218]    Total Debt: (Can be calculated field) 
         [0219]    Assets: 
         [0220]    Securities, Cash, Savings: (Enter Total Amount) 
         [0221]    Stocks: (Enter Total Amount) 
         [0222]    Bonds: (Enter Total Amount) 
         [0223]    Other Assets: (Enter Total Amount) 
         [0224]    Total Assets: (Can be calculated field) 
         [0225]    Are you guarantor to any debts of others? (YES/NO) 
         [0226]    Are there any liens on your home: (YES/NO) 
         [0227]    Are there any liens on any assets in your portfolio: (YES/NO) 
         [0228]    Current debt payments per month: (Can be calculated field) 
         [0229]    Current Income per month: (Can be calculated field) 
         [0230]    Ratio of current debt to current income: (Can be calculated field) 
         [0231]    % of income available for mortgage: (Can be calculated field) 
         [0232]    In accordance with aspects and embodiments of the present embodiments described above, a signature of the borrower can be captured on the data device such as to warrant completeness and accuracy of financial information provided by the borrower, for example. In addition, the signature of the loan officer or other financial professional can be captured and stored in association with a service report generated during inspection of the financial information of the borrower. 
         [0233]    It can be appreciated by those skilled in the art that various aspects of the present embodiments described hereinabove with respect to machines can be functionally and analogously applied to the present operational example within the scope of the present embodiments. 
         [0234]    In other example aspects of the present embodiments, use of the time/date stamping functionality associated with login, completion of checklists, and/or other functions performed on a data device  6  can provide a time card function for an organization or other entity employing aspects of the present embodiments. The time card function can include one or more data screens for receiving and/or storing relevant information associated with the service technician, details of service operations to be performed, hours worked on service operations, mileage information, mileage charge data, time/date information, cycle time information, overtime hours worked on service operations, salary rates, and/or other time card related information. The time card function can be used to record, review and track employee work performance and activities such as, for example, a cycle time or times associated with work activities of a maintenance person performing one or more service operations on an inspected item. 
         [0235]    In other example aspects of the present embodiments, the time/date when a service technician logs into a data device in response to a customer complaint about an inspected item can be collected and stored. Based on the time/date of the customer complaint, the time/date of the technician login responding to the complaint, and/or other factors, the service administrator  12 , for example, can communicate a prompt to the service technician as reminder of the need to perform a follow-up activity in association with the customer complaint. Follow-up activities can include, without limitation, a prompt for the service technician to call the customer to discuss the customer complaint and what was done in response to the customer complaint, a reminder to close out a work order number, and/or other types of follow-up activities. In another aspect, the elapsed time from initiation of customer complaint to a follow-up activity notifying the customer of resolution of the complaint can be tracked, stored, and/or analyzed as a customer response time calculation suitable for assessing customer service effectiveness of an entity/organization providing service operations to the customer. 
         [0236]    The term “computer-readable medium” is defined herein as understood by those skilled in the art. It can be appreciated, for example, that method steps described herein may be performed, in certain embodiments, using instructions stored on a computer-readable medium or media that direct a computer system to perform the method steps. A computer-readable medium can include, for example, memory devices such as diskettes, compact discs of both read-only and writeable varieties, digital versatile discs of all varieties (e.g., DVD&#39;s), optical disk drives, and hard disk drives. A computer-readable medium can also include memory storage that can be physical, virtual, permanent, temporary, semi-permanent and/or semi-temporary. A computer-readable medium can further include one or more data signals transmitted on one or more carrier waves. 
         [0237]    As used herein, a “computer” or “computer system” may be, for example and without limitation, either alone or in combination, a personal computer (PC), server-based computer, main frame, microcomputer, minicomputer, laptop, personal data assistant (PDA), cellular phone, pager, processor, including wireless and/or wireline varieties thereof, and/or any other computerized device capable of configuration for processing data for either standalone application or over a networked medium or media. Computers and computer systems disclosed herein can include memory for storing certain software applications used in obtaining, processing, storing and/or communicating data. It can be appreciated that such memory can be internal or external, remote or local, with respect to its operatively associated computer or computer system. The memory can also include any means for storing software, including a hard disk, an optical disk, floppy disk, ROM (read only memory), RAM (random access memory), PROM (programmable ROM), EEPROM (extended erasable PROM), and other like computer-readable media. 
         [0238]    In accordance with various embodiments discussed herein, wireless communication may be, for example and without limitation, communicated by satellite communications, infrared frequency, radio frequency, and/or communicated in accordance with a protocol such as IEEE 802.11, for example, among other types of wireless communication suitable for application to the present methods and systems. 
         [0239]    It is to be understood that the figures and descriptions of the present invention have been simplified to illustrate elements that are relevant for a clear understanding of the present invention, while eliminating, for purposes of clarity, other elements. Those of ordinary skill in the art will recognize, however, that these and other elements may be desirable. However, because such elements are well known in the art, and because they do not facilitate a better understanding of the present invention, a discussion of such elements is not provided herein. 
         [0240]    It can be appreciated that, in some embodiments of the present methods and systems disclosed herein, a single component can be replaced by multiple components, and multiple components replaced by a single component, to perform a given function or functions. Except where such substitution would not be operative to practice the present methods and systems, such substitution is within the scope of the present invention. 
         [0241]    Examples presented herein are intended to illustrate potential implementations of the present method and system embodiments. It can be appreciated that such examples are intended primarily for purposes of illustration. No particular aspect or aspects of the example method and system embodiments described herein are intended to limit the scope of the present invention. 
         [0242]    Use of language, nomenclature, numbering, and/or formatting is not intended to limit the scope of the present embodiments. Use of the “RR” for designation of “recommended repair” situation, for example, can be readily replaced by another functionally equivalent designation based on language, culture, customs, trade or industry practices, or other factors of a given environment in which service operations on an inspected item are performed. 
         [0243]    It should be appreciated that figures presented herein are intended for illustrative purposes and are not intended for use as construction drawings. Omitted details and modifications or alternative embodiments are within the purview of persons of ordinary skill in the art. Furthermore, whereas particular embodiments of the invention have been described herein for the purpose of illustrating the invention and not for the purpose of limiting the same, it will be appreciated by those of ordinary skill in the art that numerous variations of the details, materials and arrangement of parts may be made within the principle and scope of the invention without departing from the invention as described in the claims.