Patent Publication Number: US-9904910-B1

Title: System controlled by data bearing records

Description:
TECHNICAL FIELD 
     Exemplary embodiments include systems controlled by data bearing records which may be classified in CPC G 06 K 17/00; USPC 235/375. 
     BACKGROUND 
     Vehicle collisions are a common occurrence. Repairs often must be made to restore the vehicle to operating condition and to repair the cosmetic appearance of the vehicle to restore its value. Repair parts to repair the damaged vehicle must be identified and furnished to a vehicle repair entity (“VRE”) in order to accomplish making the repairs. Systems and methods for identifying the vehicle and proper repair parts for the damaged vehicle and furnishing the correct parts to the VRE may benefit from improvements. 
     SUMMARY 
     Exemplary embodiments include systems and methods by which repair parts necessary for the repair of damaged vehicles are determined and furnished to a vehicle repair entity responsive to data bearing records. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIG. 1  is a schematic view showing exemplary steps that are carried out in connection with repair of a damaged vehicle. 
         FIG. 2  is a schematic view that shows the entities involved in the repair of a damaged vehicle and the activities of each. 
         FIG. 3  is a schematic view of an exemplary system that is used in connection with providing vehicle collision repair parts. 
         FIG. 4  is a schematic view of functional elements included in parts pricing circuitry (PPC) of an exemplary system. 
         FIG. 5  is a schematic view of exemplary logic flow associated with providing authorized access to the functions of the PPC by a repair estimate calculation circuit (RECC) associated with a collision estimating system (CES). 
         FIG. 6  is a listing of exemplary program objects utilized by the PPC in connection with communication with an RECC. 
         FIGS. 7, 8, 8A, 9, 10, 11, 12, 13 and 14  describe the objects listed in  FIG. 6  and the fields associated with each. 
         FIG. 15  is a schematic view listing the methods associated with the objects described in  FIG. 6 . 
         FIG. 16  is a schematic view representing the methods and logic flows executed in a session between an RECC and the PPC of an exemplary embodiment. 
         FIGS. 17, 18, 18A, 19, 20, 20A, 20B, 20C, 21, 21A, 22, 22A, 22B and 22C  describe exemplary methods which are carried out in connection with the interaction between the PPC and an RECC and includes examples of the requests and results associated with each. 
         FIGS. 23 and 23A  describe an exemplary batch process which can be used with the exemplary PPC to process large amounts of needed parts records (NPRs) through the PPC to obtain parts pricing data. 
         FIG. 24  shows exemplary session communications and logic flow of the PPC in conjunction with an auto dealer parts order circuit (ADPOC) for purposes of gaining authorized access to functions of the PPC and for purposes of fulfilling parts orders. 
         FIG. 25  is a listing of program objects of the PPC with methods that are invoked in communication sessions with an exemplary ADPOC. 
         FIG. 26  is a listing of methods associated with the objects listed in  FIG. 25  and the functions carried out by each. 
         FIG. 27  is a schematic view of session communications and logic flow carried out between the PPC and an exemplary ADPOC. 
         FIGS. 28, 28A, 29, 29A, 30 and 31  are schematic descriptions of each of the objects referred to in  FIG. 25 . 
         FIGS. 32, 32A, 32B, 33, 34, 34A and 35  are schematic descriptions of the methods that are invoked by the objects listed in  FIG. 25  with examples of requests and results associated with each. 
         FIG. 36  is a schematic view listing types of collision parts which are procured and delivered to vehicle repair entities through operation of the exemplary embodiment. 
         FIG. 37  is a schematic view showing factors that are considered in connection with program logic of the PPC to determine pricing associated with collision parts. 
         FIG. 38  is a schematic view showing factors that are utilized by the program logic associated with the PPC to determine collision parts pricing information and the source of the data utilized in connection with the program logic. 
         FIG. 39  shows schematically options for interfacing with the PPC for purposes of determining pricing for collision parts. 
         FIG. 40  is a schematic view listing the work flow of an auto dealer in connection with quoting, ordering and processing rebates related to sales of collision parts. 
         FIG. 41  is a schematic view showing different processes by which the exemplary PPC interfaces with other systems for purposes of providing pricing for vehicle collision parts. 
         FIGS. 42-45  disclose exemplary output screens produced through operation of the PPC. 
         FIG. 46  shows schematically options for an ADPOC to produce invoices for collision parts. 
         FIG. 47  is a schematic view related to the import of data stored by the PPC into an ADPOC function. 
         FIG. 48  is a schematic view representing options by which an auto dealer may present claims to the manufacturer of the OE part for reimbursement related to the dealer&#39;s sales of such parts. 
         FIG. 49  is a schematic view showing the streamlined methodology for the submission of rebate claims to the vehicle manufacturer for OE parts sold by the auto dealer. 
         FIG. 50  is a schematic view describing methods by which the PPC may be operated to help an operator of an ADPOC to sell an OE part to a vehicle repair entity when a non-OE part has originally been specified. 
         FIGS. 51, 51A and 52  are a schematic view describing program logic carried out by the PPC in connection with facilitating the substitution of an OE part for a non-OE part otherwise specified. 
         FIGS. 53 and 54  show schematically a system for routing orders for vehicle repair parts that may be placed by a VRE or other entity. 
         FIGS. 55 and 56  are a schematic representation of an exemplary logic flow that is carried out by system circuitry in connection with the system for routing orders. 
         FIGS. 57 through 59  are exemplary user interface outputs produced on display devices associated with the exemplary order routing system. 
         FIG. 60  is a schematic view of components which may be included in system circuitry utilized in connection with the exemplary order routing system. 
     
    
    
     DETAILED DESCRIPTION 
     Referring now to the drawings and particularly to  FIG. 1 , there is shown therein schematically a series of activities that are carried out in exemplary embodiments in connection with the repair of collision damage to vehicles. In an exemplary arrangement, the damage to the vehicle is first evaluated as represented in step  10 . As represented in step  12 , the evaluation proceeds to determine which parts of the vehicle need to be replaced. This includes, for example, determining that bumpers, sheet metal, window glass, lights, bezels, fascias and other items have been damaged to the point of a requirement that they must be replaced. Such parts may include both parts that are visible as well as parts that are not visible such as parts that are in the frame and substructure of the vehicle such as suspension struts, steering boxes, shift linkages, control arms, etc. 
     The sources of available repair parts and the cost thereof are determined as represented by step  14 . The cost of labor is also determined as represented in step  16 . Labor costs include the necessary dismantling of the damaged parts, repair of the components that can be repaired that were originally associated with the vehicle, replacing parts that cannot be repaired with the replacement parts, and also doing the necessary painting and other cosmetic work that is required to restore the value of the vehicle to its pre-collision status. 
     As represented by step  18 , a vehicle repair entity (VRE) must be retained to do the work necessary to repair the damaged vehicle. In some cases, the vehicle repair entity is the same entity that conducts the evaluation of what needs to be replaced. In other instances, the individual or entity that owns the vehicle selects the VRE to do the work. In still other instances, an insurance company or other entity that pays for all or part of the repairs selects the VRE. Once the VRE is selected, the VRE must acquire the necessary repair parts to perform the repairs. In some instances, the VRE has some discretion as to the source of the repair parts. In other instances, the VRE may be required to acquire the parts from the sources that have been specified by an insurance company, leasing company or other entity that has submitted the repair order for the vehicle. In many cases the VRE is free to provide better quality parts than may have been specified in the repair order. This may be done, for example, to avoid having to rework and adjust non-OE parts and to promote customer satisfaction. Finally once the VRE has prepared all the necessary parts, the repairs are carried out as represented in step  22 . Exemplary embodiments may include features like those described in U.S. Provisional Application 62/193,178 filed Jul. 16, 2015 the disclosure of which is incorporated herein by reference in its entirety. 
     As represented in  FIG. 2 , the entities involved in a repair activity often include a company responsible for payment such as an insurer represented  24 . The company will generally obtain information from suppliers such as auto dealers, after market suppliers, suppliers of used parts such as salvage dealers, organizations who calculate the amount of labor to perform work and other activities associated with repairs. As previously mentioned, such responsible companies are frequently responsible for preparing estimates of costs associated with the repair of damage as well as repair orders that are given to vehicle repair entities. Such companies are also generally responsible for all or at least a portion of the costs associated with conducting repairs. 
     The vehicle repair entity schematically represented  26  is most often a “body shop” or a “collision center” that has the capability to repair damaged vehicles. In some cases, the VRE may be an independent entity. In other situations, the VRE may be part of a dealer network. This may include an auto dealer network including a body shop portion of the repair center associated with an auto dealer that sells and services the vehicles of a particular manufacturer. Sometimes the body shop of an auto dealer that sells one brand of vehicle will repair other brands of vehicles that it does not sell. In other situations, the VRE may include repair centers operated by franchisees or other networks of such suppliers. 
     As previously mentioned, it is the VRE&#39;s responsibility to procure the parts necessary to repair the damaged vehicle. The parts used to repair damaged vehicles most desirably include new original equipment (OE) parts that are made under the auspices of the vehicle manufacturer that manufactured the vehicle. Such OE parts are available for purchase from auto dealers such as auto dealer  28  who sells new vehicles made by the manufacturer as well as OE repair parts from that manufacturer. It should be understood that the reference to auto dealers herein may refer to dealers in vehicles of any type such as for example trucks, motorcycles, and recreational vehicles. Auto dealers also generally engage in the business of servicing vehicles made by the manufacturer that the dealer represents as well as other brands. As previously mentioned, vehicle dealers may also perform the VRE function to repair damaged vehicles. 
     New OE parts for collision repairs are generally procured by making a purchase from the auto dealer  28 . Commonly the auto dealer will have a warehouse or other stock which has an inventory of vehicle repair parts that are available for purchase. These parts which the auto dealer has in stock are purchased from the vehicle manufacturer  30  or a manufacturer authorized source so that the auto dealer has a variety of collision repair parts readily available. For parts that the auto dealer  28  does not have immediately available that a VRE requests, the auto dealer may order such parts and have them delivered by the vehicle manufacturer  30 . It should also be noted that commonly vehicle manufacturers provide certain rebates and incentives to their dealers in connection with the sale of items. This includes the sale of collision parts. Thus for example the auto dealer  28  may pay a “dealer price” to the auto manufacturer  30  in order to obtain a collision part (for example, a right front fender for a 2013 Buick Regal). However, when the auto dealer later sells that part to an end user the auto dealer will receive a rebate from the manufacturer for having made the subsequent sale of that part. Such sales may be to a body shop or other VRE, for example. Alternatively the sale may be made by the auto dealer to the person owning the vehicle that is repaired by the auto dealer in their VRE operation. Of course it should be understood that these sales scenarios are exemplary. 
     Referring again to  FIG. 2 , VREs also may acquire repair parts from an aftermarket parts supplier  32 . Aftermarket parts suppliers  32  are generally independent of auto manufacturers. They produce parts that have “will fit” functionality with OE parts. Such aftermarket parts are generally ones for which the vehicle manufacturer does not have patent protection or other form of protection to prevent reproduction. Aftermarket parts suppliers will generally produce an aftermarket part corresponding to an OE part when there is sufficient demand for the part due to the number of collision situations for the types of vehicles that use the part. Often aftermarket parts are less expensive than the corresponding OE part. Further aftermarket parts sometimes do not have the same function, fit and finish quality as an OE part that they are meant to replace. This can require the VRE to have to invest labor to improve the properties of the aftermarket part so it can be satisfactorily used to repair the damaged vehicle. However, in some cases, the VRE does not have discretion to use an aftermarket part in lieu of an OE part. This may be, for example, in situations where the owner of the vehicle or the insurance company that insures the vehicle determines that the vehicle is sufficiently new, has low mileage or is a particular model for which aftermarket parts are not acceptable. Such policies help to preserve the value of the designated vehicle. 
     Another source of parts for VREs are salvage and/or auto recycling operations  34 . Salvage and/or auto recycling operations which are sometimes referred to as “junkyards” provide used parts. Most often the used parts are from a vehicle that has been totaled and scrapped but on which the particular part was not significantly damaged such that it can be reused. Used parts can have highly variable quality. Further the use of the used parts by the VRE may require the VRE to engage in significant part remediation in order to restore the part to a satisfactory fit and finish. However, used parts often have a lower price than aftermarket or OE parts. 
     In each case, the vehicle repair entity  26  will acquire the parts needed for repairing the vehicle and will make the appropriate payments to the entities who supply the parts. In some cases, for a particular repair, the VRE may acquire parts from all types of sources including OE parts from dealers, aftermarket parts from aftermarket resellers and used parts from auto salvage/recycling operations. In some situations a VRE may acquire parts through a system like that described in U.S. Pat. No. 8,615,441 and/or U.S. patent application Ser. No. 14/032,932 filed on Sep. 20, 2013, the disclosures of each of which are incorporated herein by reference in their entirety. 
       FIG. 3  represents an exemplary system that is used to provide collision parts to vehicle repair entities and which can be operated to more efficiently deliver such parts and provide for higher quality vehicle repairs. 
     A damaged vehicle requiring repairs  36  is shown schematically. The exemplary system includes a repair estimate calculation circuit (RECC)  38 . The exemplary RECC is utilized by an entity that evaluates the damage to the damaged vehicle  36 . In the exemplary embodiment, the RECC comprises one or more circuits including data processors which for purposes hereof corresponds to any electronic device that is configured via circuit executable instructions that can be implemented in either hardware circuits, software, firmware or applications that are operative to enable the circuits to process data and carry out the other actions described herein. For example, the circuits may include circuits that correspond to one or more or a combination of a CPU, FPGA, ASIC or any other integrated circuit or other type of circuit that is capable of processing data. The processors may be included in a computer, server or other type of electronic device. Further, the RECC may include data stores that correspond to one or more of volatile or non-volatile memories such as random access memory, flash memory, magnetic memory, optical memory, solid state memory or other devices that are operative to store computer executable instructions and data. Computer executable instructions may include instructions in any of a plurality of programming languages and formats including, without limitation, routines, subroutines, programs, threads of execution, objects, methodologies and functions which carry out the actions such as those described herein. Structures for the RECC may include, correspond to and utilize the principles described in the textbook entitled Microprocessor Architecture, Programming, and Applications with the 8085 by Ramesh S. Gaonker (Prentiss Hall, 2002), which is incorporated herein by reference in its entirety. Of course it should be understood that these circuit structures are exemplary and in other embodiments, other circuit structures for storing, processing, resolving and outputting information may be used. 
     In the exemplary arrangement RECC is operated to determine the repair parts necessary to repair the vehicle  36  that has been damaged in the collision. In order to carry out this function, the exemplary RECC may execute collision estimating programs that are commercially available to indicate all of the parts that make up the various areas of vehicles that may be damaged in collisions and to provide the part numbers or other identifying information associated therewith. Such commercial programs may be utilized by an estimator or other personnel for purposes of comparison to the damaged vehicle to note which parts have been damaged and require replacement. The RECC generally includes input and output devices included therewith, such as an output device in the form of a screen  40 . Input devices such as for example a keyboard  42  and a mouse  44  or a touch screen may be utilized to provide inputs to the RECC so as to provide inputs thereto. The RECC may also include or be in operative connection with one or more readers. Such readers may include a bar code reader, an RFID tag reader, a camera or other image capture device or other device capable of reading indicia. Exemplary embodiments may include circuit executable instructions which are operative to analyze read indicia such as captured image data, resolve data corresponding thereto, and provide output signals corresponding to the indicia such as signals corresponding to alphanumeric or other characters that are read through operation of the reader. 
     Circuit executable instructions that may be utilized in connection with an RECC sometimes cause such systems to be referred to as collision estimating systems (CES). CES instructions may provide not only the ability to identify and designate needed repair parts to replace parts that have been damaged, but also the amount of labor that is required to remove damaged parts, repair damaged parts to be reused, to install new parts and to perform other functions such as painting, clear coating, sound deadening and the like. It should be understood that in some arrangements, CES instructions may be utilized to determine the nature of damage incurred both to chassis, body and mechanical components of the vehicle and identify the necessary components for the repair of each. 
     As represented in  FIG. 3 , in some arrangements the RECC may comprise a stationary device located in a vehicle repair entity facility or in a facility which has the function of estimating vehicle damage. However, in alternative arrangements the RECC may comprise or be in operative connection with one or more portable terminals which have the capability to be taken to a location of a damaged vehicle or otherwise used on a portable basis. Such portable terminals may include, for example, WiFi or other wireless interfaces so as to enable the communication thereof with other components of the system as later described herein. For example in some exemplary arrangements, the RECC may be in the form of a portable handheld device  46  which includes a reading device which comprises a camera  47 . Some portable devices may be multi-function devices that are capable of performing multiple functions in addition to functions associated with the RECC. Other types of portable devices may include specially designed configurations such as the portable estimating terminal  48  shown. Estimating terminal  48  may include output and input devices operable by a user. Such input devices may include one or more readers. Such readers may include readers such as a camera or other image capture device, bar code readers, RFID tag readers or other readers suitable for reading optical, RF or other forms of indicia. Of course it should be understood that the RECC devices shown are exemplary and in other arrangements, other approaches may be used. 
     In some exemplary embodiments the portable device included or associated with the RECC is operable to utilize the reader associated therewith to read one or more tags  49  which are in operative connection with the damaged vehicle. The tag or tags in exemplary arrangements are usable to provide vehicle identifying information which may include or be usable to identify repair component identifying information associated with the damaged vehicle. For example in some exemplary arrangements the tag may include vehicle identifying indicia in the form of a Vehicle Identification Number (“VIN”). The tag may include alphanumeric or other optically readable characters which comprise the VIN. One or more images including VIN data may be captured through operation of a camera or other optical reader on the portable device or other reader in operative connection with the RECC. Character recognition circuit executable instructions operable in connection with RECC are operative to resolve data which corresponds to the characters in the VIN data. In exemplary embodiments the RECC is operative to utilize the characters of the VIN to determine vehicle identifying data, such as the vehicle make, model year, model, engine type, manufacture date, manufacture location, vehicle color, vehicle transmission type, vehicle suspension features, trim levels, option packages, and other characteristics or options included on the vehicle at the time of manufacture. Of course these examples of vehicle identifying data that can be determined using the VIN characters are exemplary. In exemplary arrangements the vehicle identifying data corresponding to the indicia on the one or more tags can be determined based on stored data included in one or more data stores associated with the circuits of the RECC. Alternatively the portable device may be selectively operative to communicate with other devices and systems which enable the resolution of vehicle identifying data responsive to the read indicia. 
     In other arrangements the reader may be operative to read machine readable indicia from one or more tags. Such tags may include one or two dimensional bar codes which correspond to information usable to determine one or more items of vehicle identifying data. Such indicia may be read through operation of the reader in operative connection with the REC. The RECC may then be operative to resolve the characters or other data corresponding to the read indicia responsive to circuit executable instructions. The RECC is then operative to resolve the vehicle identifying data corresponding to the read indicia. 
     For example in some arrangements vehicle components are marked with bar code tags or other indicia which identify the vehicle and/or the particular part. In some exemplary arrangements the indicia may be read from a damaged part in order to determine the one or more repair parts needed to repair the damaged vehicle. In alternative arrangements indicia including lists of components used in connection with assembly of a vehicle may be included in or on the vehicle. The indicia may be read from such build sheets which correspond to tags for purposes of determining vehicle identifying information which is usable to identify repair components. 
     In some exemplary arrangements indicia may be read through operation of the at least one reader in the form of RF signals. For example in some exemplary arrangements, vehicle components or assemblies may include RFID tags which provide indicia to a reader in the form of RF signals that can be used to resolve vehicle identifying data. Alternatively or in addition, electronic control modules or other circuitry associated with components in the vehicle may be interrogated through RF or other electronic signals, and caused to provide outputs which correspond to vehicle identifying data and other information usable to identify needed vehicle repair parts. In some exemplary embodiments some control modules may include internal diagnostic capabilities which can produce outputs that can be interpreted to identify circuits or other connected components or modules which have been damaged and require replacement. Of course these approaches are exemplary and depend on the capabilities of the components of the damaged vehicle. 
     In other exemplary arrangements, the tags which are read through operation of the reader may include license plates, fleet vehicle identification stickers or other things which include readable indicia and which can be used to resolve vehicle identifying data. In exemplary arrangements the data resolved in response to the indicia read by the reader is usable by the RECC to obtain the vehicle identifying data. Such tag data may be used to query a public or private database in order to obtain VIN data which can be used to obtain other items of vehicle identifying data. In other arrangements the read indicia may be used to recover other information which may be held by a fleet operator, manufacturer or other company in order to obtain the vehicle identifying data which is usable to identify needed repair parts. Of course these approaches are exemplary. 
     In exemplary embodiments the RECC is operative responsive to inputs to produce a needed parts record (NPR). In some exemplary arrangements the NPR is generated through operation of the RECC or CES responsive to VIN or other vehicle identifying data. In some exemplary arrangements the vehicle identifying data is resolved responsive to indicia read through operation of the reader. Alternatively in other arrangements vehicle identifying data may be manually input to the RECC through at least one input device. In other arrangements data is input both manually or through operation of one or more readers. 
     In some exemplary arrangements the RECC and/or CES is operative responsive to the resolved vehicle identifying data, to provide display outputs on a terminal screen or display which corresponds to repair parts and/or other components or items which may be needed in connection with repair of the damaged vehicle. In some exemplary arrangements the RECC is operative to provide screen output responsive to the vehicle identifying data including drawings, exploded views, bills of material, schematics or other information related to components which comprise the particular vehicle which has been damaged. Such schematic information may be presented based on the vehicle identifying data and stored information in data stores associated with the RECC. In other embodiments the data to produce screen outputs may be obtained from one or more data sources remote from the RECC and accessible through one or more networks. 
     In exemplary arrangements the operator of the RECC is enabled to provide selection inputs which cause the display of drawings, lists or other graphics which show vehicle components in the area of the vehicle where damage has occurred. In exemplary arrangements the user is enabled to selectively view or receive identifying information regarding components in the damaged area. In some exemplary arrangements the user is enabled to provide selection inputs that identify the needed repair parts. Such inputs may include providing touch screen inputs on a portable terminal or pointer and mouse click inputs on a stationary terminal. Responsive to such inputs the exemplary RECC is operative to produce the NPR, which in the exemplary embodiment includes descriptions and part numbers for needed repair parts. 
     In some arrangements the RECC is operative to include in the NPR indicia corresponding to vehicle identifying data. Such data may include for example, the vehicle make, model, year, VIN and other data. Such other data may include for example, the mileage of the vehicle, the state where the vehicle is located, the VRE, the entity responsible for the cost of repairs or other information that is required by the RECC to be manually input or otherwise read or resolved from other data, and included in the NPR. Of course as previously discussed the RECC may operate to estimate other costs such as time and labor costs associated with replacing the identified parts in the NPR and repairing other components. Of course these features are exemplary and in other embodiments other, different or additional features and functions may be provided. 
     As represented schematically in  FIG. 3 , the RECC can communicate in one or more networks indicated  50 . In exemplary arrangements the network  50  may include one or more electronic communication networks through which devices may communicate in the manner hereinafter described. Such networks may include wired or wireless communication networks, RF networks, satellite networks or other suitable networks for providing communications. Private networks may be used for communications or alternatively widely available public networks such as the Internet may be utilized in connection with exemplary embodiments. It should be understood that a single network is shown in  FIG. 3  for simplicity for communication with numerous devices. However, this is exemplary and embodiments may utilize numerous different interconnected communication networks. 
     In the exemplary system shown in  FIG. 3 , one or more vehicle repair entities communicate in the system through a respective VRE circuit, schematically represented  52 . The exemplary VRE circuit  52  may include one or more circuits including processors and data stores of the types previously described in connection with the RECC. The VRE circuit  52  includes input and output devices schematically represented  54  which enable operators of the VRE circuitry to provide inputs and receive outputs therefrom. The VRE circuitry is configured to communicate with the other devices included in the system through the one or more networks  50 . The VRE circuit may also include portable terminals including readers like those previously described. 
     The exemplary system further includes an auto dealer parts order circuit (ADPOC)  56  and another ADPOC  58 . Each ADPOC structure is comprised of circuits which may include processors and data stores of the types previously described in connection with the RECC. ADPOC  56  has input and output devices  60  included therewith. Likewise ADPOC  58  has input and output devices  62  included therewith. Such input devices may include keyboards, computer mice, touch screens or other types of suitable input devices. Output devices may include displays of various types or other suitable output devices for conveying information to users and/or other connected devices. Each ADPOC is operated by a respective auto dealer for purposes of identifying, pricing and ordering collision vehicle repair parts as will be described in greater detail hereinafter. Each ADPOC may operate programs and other circuit executable instructions associated with a dealer management system (DMS). DMS systems may be operated by auto dealers to perform the functions that are commonly associated with auto dealerships. This includes operations like preparing invoices, managing inventory and other dealer functions. The capabilities of different DMS systems depends on the nature of the type of program that is used. 
     Each ADPOC is in operative connection with the one or more networks  50 . The functions carried out by an exemplary ADPOC will be later discussed herein in detail. 
     In the exemplary system schematically represented in  FIG. 3 , the auto dealer associated with ADPOC  56  is associated with a particular vehicle manufacturer. In the exemplary arrangement, the auto dealer functions as the sales outlet for the vehicles manufactured by the respective manufacturer and also sells the original equipment (OE) parts that the manufacturer produces for its vehicles. The manufacturer with which the auto dealer who operates ADPOC  56  is associated, operates at least one manufacturer fulfillment circuit schematically indicated  64 . Circuit  64  is comprised of circuitry which may include processor structures and data store structures of the types previously described in connection with RECC. The manufacturer fulfillment circuit  64  includes input and output devices  66  which may be of the types previously described. The manufacturer fulfillment circuit  64  is configured to communicate in the one or more networks  50 . Further in the exemplary arrangement the manufacturer fulfillment circuit  64  may also be in more direct communication with its dealers ADPOC  56  through an alternative direct network  68 . Such a network  68  may be a nonpublic network that the manufacturer uses to communicate with its dealers. Such dealer networks may be utilized to enable dealers to place orders for products and services with the manufacturer. Alternatively or in addition, such networks may be utilized to update service diagnostics, communicate information regarding service bulletins, disseminate information about recalls, implement promotional incentives, manage inventory between different dealers or otherwise perform functions that the manufacturer carries out in conjunction with its respective dealer network. Of course it should be understood that these functions are merely exemplary of those types of functions and activities that an auto manufacturer may carry out in conjunction with its dealers. 
     Similarly the dealer operating the exemplary ADPOC  58  is associated with a different vehicle manufacturer. The manufacturer operates a manufacturer fulfillment circuit  70  which has a structure and features like those previously described in connection with circuit  64 . The exemplary manufacturer fulfillment circuit  70  includes input and output devices  72 . The manufacturer fulfillment circuit communicates with the one or more networks  50  as well as in a network  74  which is used to communicate with its dealer organizations. 
     It should be understood that the exemplary system shown in  FIG. 3  is simplified and that generally systems may involve numerous entities that operate respective RECC devices, numerous different VRE entities that operate VRE circuits, numerous different dealers associated with different manufacturers of vehicles and who supply collision parts for the vehicles that their respective associated manufacturers have produced. 
     The exemplary system further includes at least one parts pricing circuit (PPC)  76 . The exemplary PPC is comprised of circuits which may include processors and data stores having the structures like those described in connection with the RECC. The exemplary PPC includes one or more input and output devices schematically represented  78  like those previously discussed. In the exemplary arrangement, the PPC may comprise circuitry which is referred to herein as mypricelink.com or MPL which is operated by OEConnection of Richfield, Ohio. Of course, this arrangement is exemplary and in other embodiments, other arrangements and structures including distributed processing structures or networks may be utilized to perform the functions described herein in connection with the PPC. 
     In the exemplary arrangement the PPC operates as described in greater detail hereafter to provide pricing for vehicle repair parts to operators of RECC system devices for purposes of preparing estimates which are alternatively referred to herein as repair orders, that are used by companies such as insurers responsible for payments and other operators of collision estimating systems. The exemplary PPC is also operative to enable auto dealers utilizing their respective ADPOC to recover information regarding repair parts which are associated with estimates and pricing records for damaged vehicles. Such records may be recovered in response to inquiries by vehicle repair entities or other entities who require such parts to make repairs. The dealer may utilize their ADPOC to identify the needed parts and place the requisitions or orders for such parts so that they are furnished to the VRE responsible for repair of the vehicle. Further the exemplary PPC may be utilized to enable the dealer to provide to the VRE a higher quality part such as an OE part, at a price that is equal to or better than an aftermarket or used part that has been specified in an estimate to be used in connection with repair of the vehicle. Further the exemplary PPC may be operative to track additional rebates or incentives that a respective auto manufacturer may offer to a dealer in connection with reducing the price for collision parts as necessary to meet the competition of a lower priced aftermarket or used part that has been specified originally in connection with the repair activities for a vehicle. Further the exemplary PPC can perform the additional functions and capabilities that are described herein. 
       FIG. 4  shows schematically the functional makeup of the exemplary PPC  76 . In the exemplary arrangement the PPC comprises circuit structures including processor structures  80  that may be of the types previously described. The exemplary PPC further includes data stores  82  having the structures of the types previously described. Further the exemplary PPC includes interface circuitry which is suitable for enabling the PPC to communicate with input and output devices. Interface circuitry is also operative to enable the PPC  76  to communicate with other devices through the one or more networks  50 . The exemplary PPC may also include other circuitry  86  such as integrated circuits that are operative to perform additional functions such as security functions. This may include for example encryption capabilities, the storage of digital signatures and/or certificates, public or private encryption keys, or other suitable structures. Such circuitry  86  may also include security devices such as a trusted programming module (TPM) as well as other circuitry associated with achieving the desired operations of the PPC. 
     As schematically represented in  FIG. 4 , the exemplary data stores  82  include stored circuit executable instructions which are in the form of program instructions that can be executed by the circuitry of the PPC. Such functions may include, for example, instructions which limit access to the functions performed by the PPC to certain authorized devices or users which are schematically indicated  88 . Other exemplary instructions include program objects associated with determining parts pricing and communicating with external devices. Such instructions are schematically indicated  90 . The exemplary PPC also includes instructions associated with the logic associated with applying discounts and rebates for parts for which prices are provided. This is represented schematically by instructions  92 . Of course these instructions are merely illustrative of some of the high level instructions that may be included in the exemplary PPC data stores and in other arrangements, different, other and/or additional types of instructions may be utilized. 
     The exemplary data stores  82  further include stored instructions corresponding to records. Such records may include, for example, records regarding different parts which can be priced through the system schematically indicated  94 . Other records may include records corresponding to companies or other payors who pay for collision parts. These records schematically indicated  96  may commonly include the identity of the company or other payor. They also include policies, rules and requirements of such entities. Such policies, rules and requirements may include, for example, a requirement that only OE parts be used on certain vehicles. Such requirements may be designated by the model year, make, model type, mileage or other factors associated with a given vehicle that is to be repaired. Such policies may mandate that for vehicles which fall within certain criteria, no aftermarket or used parts may be utilized in connection with the repair. However, for other vehicles the policies reflected in the records  96  may authorize the use of some such parts or particular parts which the company has determined are of suitable quality. Further in some exemplary arrangements company instructions included in the records may indicate that within certain states, cities or other geographic regions, certain requirements associated with the repair parts must be followed. For example there may be restrictions on the use of aftermarket parts to make repairs within certain states. Further, the company may have policies that mandate the use of only OE parts for vehicles that remain under lease. Additional policies may not permit the installation of used parts that originate from certain states or from certain suppliers. Numerous different requirements of entities who are responsible for specifying the character of parts that can be utilized in connection with making repairs may be included in the data and instructions represented by records  96 . 
     Further in the exemplary arrangement the data stores  82  include interchange records schematically represented  98 . In exemplary embodiments the interchange records may correspond to the interchange between OE parts and aftermarket parts. Thus for example such records may specify for a given OE part the one or more aftermarket parts that are available. Such records may also include other information regarding such parts such as specifications, sources, prices, countries of origin or other fit or finish parameters associated with such parts. Such interchange records may also include parts designation information which enables deciphering part numbering systems used by OE and aftermarket manufacturers so as to determine which parts may be substituted for others. Further exemplary arrangements may also include information regarding used parts that may be available from different sources including interchange information such as which used parts from different models of vehicles may be substituted for an aftermarket or an OE part which may be identified as usable on a vehicle that is in need of repair. Of course the information in the records  98  is exemplary and in other arrangements, other types of instructions may be included. 
     The exemplary PPC further includes records related to authorized users and/or user devices schematically indicated  100 . Exemplary user records  100  may be utilized for limiting access to only authorized users of the PPC. Such user records may also include information concerning activities by the users including the submission of parts pricing data and the creation of parts pricing records (PPRs) or other estimate data that has been stored on the system in association with vehicles to be repaired. 
     The exemplary PPC further includes parts pricing records (PPRs) schematically indicated  102 . In the exemplary arrangement the parts pricing records comprise instructions which correspond to the data associated with the repair of a damaged vehicle including the repair parts that will need to be acquired to achieve the repairs. In exemplary arrangements, the parts pricing records may include indicia corresponding to a data set of information produced through operation of a collision estimating system which specifies more than the particular vehicle for which the parts are needed and the parts. For example such records may include information about the responsible payment company, labor rates and estimates for repairs and other repair information. Such information may also include information about the vehicle repair entity who will perform the repair activities, non-OE parts that have been specified for the repair and other information that is pertinent to the repair activities that will be conducted to restore the damaged vehicle to operational condition. 
     Of course it should be understood that the exemplary types of instructions, records, structures and other features, functions and capabilities of the PPC  76  are exemplary and in other embodiments, different capabilities, structures, functions, data records and operational capabilities may be utilized. 
     In the exemplary arrangement, the PPC is operated responsive to the NPR data to provide parts pricing for purposes of estimating the cost associated with the parts necessary to repair a damaged vehicle. PPC is further operative to produce a parts pricing record (PPR) associated with the damaged vehicle or other situation for which the pricing is provided, and to store the associated data so that it can be reviewed, revised and recovered by authorized users of the system. The exemplary PPC further uses the data from the auto manufacturer regarding the parts and other data and pricing logic in order to provide a price that is appropriate for the given situation associated with the damaged vehicle. This pricing is in many cases specific to the particular vehicle, the state in which it is located, the company or other entity responsible for payment and other factors. This specific pricing is delivered for purposes of calculating the estimated cost to repair the vehicle to a vehicle repair entity (VRE), payment responsible company or other operator of a collision estimating system (CES), is stored by the PPC in parts pricing records. 
     In the exemplary arrangement, an auto dealer who is subsequently requested by a vehicle repair entity to supply the OE parts that were made by the vehicle manufacturer for purposes of repairing the damaged vehicle, may recover and review the parts pricing record (PPR) associated with the particular vehicle stored in the PPC. The auto dealer can utilize their ADPOC to review the parts, the pricing quoted and other information about the particular parts. Such other information may include, for example, the dealer cost, costs at which such parts are commonly sold at a discount to other entities in the trade such as body shops, and other information such as any rebates or incentives that the manufacturer provides to its dealers in connection with the sale of the particular parts. 
     Further in the exemplary embodiment the PPC is operative to enable the auto dealer from which OE parts are being requested, to review any aftermarket parts or used parts that have been specified for the repair. The exemplary PPC is operative to provide to the auto dealer information about original equipment parts that correspond to the aftermarket or used parts that could be offered as a higher quality substitute therefore. The exemplary PPC further provides the opportunity for further discounts for such OE parts that can be substituted and furnished in place of aftermarket or used parts to the VRE, along with additional incentives that can be offered to enable the dealer to meet the competition. This enables the dealer to offer to the VRE the option to acquire a new manufacturer OE part to use in the repair of the vehicle at a price that is at least as low as that of the aftermarket or used part that has been specified. This enables VREs to opt to select such higher quality parts which may avoid the need for them to conduct rework or otherwise deal with imperfections in the fit or quality of aftermarket or used parts. In an exemplary arrangement if the VRE elects to acquire the OE part instead of the aftermarket or used part, the exemplary PPC enables the ADPOC to be utilized for purposes of modifying the parts pricing record PPR data associated with the damaged vehicle to reflect the use of the OE part. 
     Further in the exemplary arrangement, the PPC is enabled to deliver data to the dealer&#39;s ADPOC so that the orders for the desired parts can be issued and the parts furnished or otherwise delivered to the VRE. Further in the exemplary arrangement the PPC is operative to enable the auto dealer who has been authorized to provide a discount on an OE part in order to meet the lower priced competition of an aftermarket or used part, to obtain the additional rebate compensation offered by the manufacturer in connection with achieving the sale of the OE part. In the exemplary arrangement the PPC is usable to enable the processing of the rebate request so that the auto dealer that achieved the sale of the OE part that was not originally specified, can receive the additional compensation and maintain a more suitable margin of profitability in connection with the sale of the part. 
     Of course it should be understood that these functions of the exemplary PPC are those of an exemplary arrangement and in other arrangements, different, fewer or additional functions may be carried out by a PPC. Further in other arrangements the PPC may include a number of distributed circuits and devices which carry out certain of the functions that have been described herein in connection with a single PPC. 
     Thus in the exemplary arrangement the system represented in  FIG. 3  will most commonly be operated in connection with preparation for repair of a damaged vehicle by an entity associated with an RECC determining the parts necessary to repair the vehicle. This will be done through the operation of the collision estimating system (CES) instructions that may be operated in the RECC to identify the particular parts and part numbers of parts that have been damaged. Of course as previously discussed, in exemplary arrangements such CES systems will generate numerous identifying items of information associated with the vehicle, the company associated with paying for the repairs and numerous other items of information in addition to the repair parts needed. 
     Once the repair parts that are needed have been determined in a manner like that previously discussed, the RECC will operate to send a needed parts record (NPR) through the one or more networks  50  to the PPC  76 . The exemplary needed parts record includes the identifying information associated with the vehicle as well as identifying information for each of the parts that will need to be procured by the VRE before the vehicle is repaired. Of course as will be subsequently explained, generally not only the parts data will be included in the NPR that is sent to the PPC, but other information associated with the vehicle and its repair will also be included. 
     The exemplary PPC receives the NPR information from the RECC. Responsive at least in part to the NPR and the information therein, the PPC is operative to cause a parts pricing record (PPR) to be produced. The PPR includes data corresponding to at least some of the parts that are included in the NPR that will be needed for the repair of the vehicle. The exemplary PPC also causes at least one unique identifier to be associated with the PPR. The unique identifier (ID) can be utilized to recover the PPR. In some exemplary embodiments this may be an assigned generated quote number or other system number. Further additional identifiers may be associated with the PPR. For example, in exemplary arrangements the VIN associated with the vehicle, an identifier associated with the entity requested the PPR, or other data may be utilized as an identifier or designator for the particular PPR record data. Once the PPR is generated, it is stored through operation of the PPC in the one or more data stores associated with the PPC. The PPR record data is also made accessible by the PPC to the RECC which requested the part data including parts pricing. This enables the RECC to produce a repair order record which in some arrangements may be in the form of an estimate or other document that corresponds to the repair of the damaged vehicle. In the exemplary arrangement the repair order record includes one or more of the ID values that are associated with the PPR in the records of the PPC. In the exemplary arrangement, the repair order record is utilized by the company responsible for paying for repairs, the vehicle repair entity or other entity to document the estimated cost of parts, labor and other activities associated with the repair of the particular vehicle. Further in an exemplary arrangement the repair order record and PPR data may include information concerning any aftermarket or used parts that may have been specified for use in connection with the repair of the particular vehicle. 
     To achieve the repair of the damaged vehicle, the exemplary system is operative to assign the repair order record from a RECC to a vehicle repair entity (VRE). The repair order record may be assigned in any number of different ways. In some arrangements the repair order is generated by a printer on paper and delivered to a body shop that will do the work. Alternatively the repair order record may be generated by the VRE who will perform the repair work. Alternatively or in addition, the repair order record may be generated and sent electronically through the one or more networks  50  to the VRE circuit associated with the VRE who is retained to perform the repair activity. 
     Alternatively in some exemplary arrangements the repair order record may be generated by a RECC and disseminated to a number of different prospective VREs who could perform the work for purposes of determining ones which may be able to perform the repair activity in a more timely manner or based on other criteria that meet the needs of the vehicle owner and/or the company responsible for payment. For example in situations where the owner of the damaged vehicle is entitled to the replacement vehicle during the period of repair, the company making payment for the repairs may be interested in finding the VRE that can do the repairs the most rapidly so as to minimize the replacement vehicle expense. Of course such assignment of repair order records is merely exemplary and other factors and procedures may be utilized. 
     In an exemplary repair situation, the VRE who receives the repair order record is responsible for procuring the parts necessary to achieve the repairs. In such circumstances, the VRE contacts an auto dealer who can supply the OE parts specified in the repair order record. This may be done in some situations electronically. The one or more networks  50  may be used, for example, by the VRE circuit associated with the VRE assigned to repair the damaged vehicle, to contact a selected auto dealer through an electronic message including identifying corresponding to the particular ID associated with the PPR stored in the PPC. In some arrangements the VRE circuit may be enabled to communicate with a dealer&#39;s ADPOC for purposes of causing the ADPOC to recover the PPR associated with the particular vehicle, and to request electronically that the dealer through communication with the ADPOC furnish the indicated parts. Alternatively in other arrangements the VRE who has received the repair order record associated with the damaged vehicle may contact the dealer via phone and indicate the particular vehicle, quote ID, VIN or other information that will enable the dealer to recover the PPR associated with the vehicle from the PPC. 
     When the auto dealer that the VRE wishes to deal with is contacted about the parts needed for the repair, the auto dealer utilizes the ADPOC to recover the PPR from the PPC associated with the damaged vehicle. In the exemplary arrangement the PPR will include data corresponding to the manufacturer&#39;s OE parts that have been specified in the repair order record for use in the repair of the vehicle. In the exemplary arrangement the PPR will also include the pricing and other data that was calculated by the PPC for the repair parts and included in the PPR. 
     In the exemplary arrangement, the PPC will operate responsive at least in part to data included in the PPR to provide to the ADPOC of the dealer who has been selected to furnish the parts, additional information associated with the parts. This may include the dealer&#39;s cost to obtain the parts as well as data corresponding to any rebates or incentives that the manufacturer offers in conjunction with the sale of the OE repair parts. Further in some exemplary arrangements the PPC will operate to cause an indication to the dealer through the ADPOC a trade price or industry discounted price that is normally offered to persons in the trade, such as body shops and repair facilities. The trade price enables the VRE to make a profit on the sale of the parts that corresponds to the difference between the trade price and the parts price that the VRE was authorized to charge for the parts based on the repair order record. Further in the exemplary arrangement because the dealer through the ADPOC can review the dealer&#39;s cost plus rebates and other incentives that are associated with the sale of the part, the dealer is enabled to evaluate whether it may be appropriate to offer the VRE an additional discount or other incentive to purchase additional things that are needed for the vehicle repairs from the dealer. This might include acquiring OE parts as substitutes for certain aftermarket parts that have been specified in the repair order record, and which the dealer can convince the VRE to buy from the dealer because of the additional discount. Further the dealer through the ADPOC may utilize an additional discount capability to have the VRE purchase other third party items, for example tires that might be needed for the vehicle repair, through the dealer. Of course these scenarios are exemplary. 
     Further in exemplary arrangements the PPR data that is presented to the dealer through the ADPOC may include aftermarket or used items that have been specified for the repair of the vehicle. The exemplary PPC operates to analyze identifying data associated with such aftermarket or used items (sometimes referred to herein as N-parts) and provide information to the ADPOC on the corresponding new OE parts that are available from the dealer. The exemplary PPC further operates in accordance with its programming as later discussed, to determine whether a corresponding new OE part can be furnished by the dealer in place of the N-part for a price that is no greater than the N-part. The exemplary PPC further operates in accordance with its programming to display a price on a screen or other device associated with the ADPOC that can be offered for the corresponding OE part in place of the N-part along with an additional rebate that the manufacturer of the OE part is prepared to offer to the dealer, if the OE part is sold to the VRE at the discount price indicated. 
     In the exemplary arrangement the dealer has the opportunity to offer the VRE the OE part made by the manufacturer at a price that is at or below the price indicated that the VRE would have to pay to purchase the N-part. Generally a VRE would be interested in such an opportunity as there is a much lower risk of quality and rework problems associated with an OE part compared to an N-part. Further the dealer is enabled to offer a greater discount but also receive the rebate indicated which assures the dealer a reasonable profit margin on the sale of the OE part that is substituted for the N-part. 
     In the exemplary arrangement if the VRE chooses to purchase the OE part in lieu of the N-part, the dealer through corresponding inputs and operation of the ADPOC may change the PPR associated with the vehicle in the one or more data stores associated with the PPC. Further the exemplary ADPOC is operative to process an order from the VRE for the OE parts that the VRE has decided to order from the dealer. Further in the exemplary arrangement, the ADPOC is operative to generate electronically the paperwork that will cause the requested OE parts to be furnished to the VRE. This is done either through requisitions to supply the part from the dealer&#39;s own inventory or from a warehouse or similar operation operated by the vehicle manufacturer. For example in some exemplary arrangements the ADPOC may be operative responsive to the PPR to generate one or more fulfillment records. In exemplary arrangements the fulfillment records include data corresponding to the repair parts to be furnished by the dealer to the VRE. In exemplary arrangements the fulfillment records may include human readable indicia which includes data corresponding to part numbers, part descriptions, the VIN or ID, and address or other data associated with the VRE and address or other data associated with the auto dealer. In some exemplary arrangements the fulfillment records may also include machine readable indicia that corresponds to repair parts included on the fulfillment record. In some exemplary arrangements the machine readable indicia may include bar codes or other indicia that is usable to identify and collect each vehicle repair part. In some exemplary arrangements the machine readable indicia is usable to identify storage locations for parts as well as the parts that are stored in a warehouse or similar facility. In some exemplary arrangements an automated system or semi-automated system includes suitable readers and is operative to gather the repair parts based on correspondence between the machine readable indicia in the fulfillment record and the machine readable indicia associated with the stored repair part packaging and/or locations. In such a system the readers may be in operative connection with a movable collection cart and/or automated picking or conveying structures to engage and move desired repair parts including the machine readable indicia corresponding to data included in the fulfillment record, and to collect such parts together for furnishing to the VRE either via pick up by the VRE or by delivery to the VRE via a carrier. In some exemplary arrangements the ADPOC may be operative to cause the generation of fulfillment records at multiple warehouse or other part storage locations in situations where the repair parts are not all in inventory at a single location. In some arrangements the fulfillment records may be operative to cause the repair parts to be furnished directly to the VRE such as by delivery through a carrier, while in other arrangements the parts may be collected by or shipped to the auto dealer who furnishes the parts to the VRE. Of course it should be understood that these approaches are exemplary and in other embodiments other approaches may be used. 
     Operation of the exemplary PPC to provide an RECC and the operator thereof with parts pricing data is now described in connection with  FIGS. 5-23 . In the exemplary arrangement, the PPC is configured to restrict access to the capabilities of the PPC to certain authorized users. Further the exemplary arrangement assures that if the user is authorized, they can only access those records and functions to which the particular user or RECC system is authorized to have access. 
     In the exemplary arrangement, the PPC uses software based on OAUTH 2.0 for enabling access by authorized users. The OAUTH 2.0 is a protocol that provides specific authorization flows from device applications. The OAUTH specification and associated RFCs are developed by the IETF OAUTH working group. Of course it should be understood that this approach to enabling access to the available resources of the PPC is exemplary and other approaches may be used. 
     The exemplary message and logic flows associated with authenticating an authorized RECC user to the PPC is represented in  FIG. 5 . As represented therein, the operator of the PPC which in this case is referred to as OEConnection or OEC, provides a client ID and client secret to the operator of the collision estimating system (CES and/or RECC) when they agree to participate in the use of the system including the PPC. As represented in  FIG. 5 , the RECC sends the client ID and client secret to request a token from the PPC system. As shown in  FIG. 5 , authenticating the genuineness of provided credentials causes the PPC to operate to provide an access token which enables the RECC to access the PPC and the methods available therein, for obtaining parts pricing information for a limited period of time. In the example represented in  FIG. 5 , the period of time corresponds to one hour. The token enables the RECC to have the functions performed in conjunction with the methods to be carried out to provide the RECC with parts pricing information during the time period associated with the token. If the access token expires or the RECC has an expired access token, the exemplary PPC and server associated therewith enables the RECC to acquire a new token so as to carry out further operations. 
     Further in the exemplary embodiment of the PPC, control logic is provided by the circuit executable instructions to avoid abuse of the system by authorized users who have been granted access. The access logic associated with the PPC monitors usage by individuals to determine the number of inquiries processed. If the number of parts pricing transactions carried out exceeds one or more program thresholds, the user&#39;s further access to the PPC resources is discontinued. For example in a circumstance where an authorized user is attempting to construct a price list for a broad range of parts or otherwise attempting to gain information on parts pricing from the system that is unrelated to a specific vehicle collision situation, the logic associated with the system will operate to suspend further inquiries. Further in exemplary arrangements, control logic is included in connection with the PPC so that if a particular operator of an RECC repeatedly attempts to engage in activities that suggest that they are utilizing the PPC for unauthorized purposes, the RECC system will be blacklisted and no longer allowed to access functions of the PPC. 
     In exemplary arrangements, this control logic is associated with the number of parts pricing requests processed within a given time period by the RECC. Further the control logic considers factors including the type of authorized user granted access to the system. For example in the case of an authorized user associated with the RECC and who is identified in the system as a company that makes payments for repair of numerous vehicles, the threshold for the number of permitted inquiries may be set to a very large number within a given time window or may be set as unlimited. Alternatively when the authorized user has been categorized as an independent body shop having a single location, the threshold may be programmed to be at a much lower level. In exemplary arrangements the categorization of an authorized user so as to associate each user as a particular type and assign the corresponding thresholds may be done at the time that credentials such as the client ID and client secret are issued. In this way, the entity responsible for operation of the PPC may allow access by user entities about which little is known, while still guarding against such entities having capabilities to improperly use and mine data from the system. Of course it should be understood that these approaches are exemplary and in other arrangements, other approaches may be used. 
     The exemplary PPC functions and the application programming interface (API) associated therewith for communication with RECC devices that operate as collision estimating systems (CES) is configured in the exemplary embodiment to employ the methods associated with eight program objects that are included in the instructions executed by the exemplary PPC. These eight program objects are give the designators listed in  FIG. 6 . 
     In the exemplary configuration the PPC enables its capabilities to be used in conjunction with numerous diverse and different types of systems. As a result, this enables the PPC to operate with RECC systems and CES instructions that utilize diverse platforms and programming languages. Likewise the exemplary PPC is enabled to operate in conjunction with ADPOC platforms that utilize different programming languages and dealer management systems (DMS) platforms. These capabilities are accomplished in an exemplary arrangement by the PPC communicating PPR data in a data format that can be read and used by any one of numerous computer programming languages. In the exemplary arrangement the PPC communicates in the JavaScript object notation (json). Json is a lightweight data interchange format that is language independent. It has the advantage that it is “self describing” to other programs and is easy to interpret. It is a text-based language that uses JavaScript syntax. Of course it should be understood that in other arrangement other data formats that are suitable for being read and used by numerous platforms and programming languages may also be used. This includes markup language formats such as XML and extended XML formats. Of course it should be understood that these approaches are exemplary and while it is desired in the exemplary arrangement to have the PPC be interoperable with numerous other types of systems, other arrangements may operate based on specific proprietary technologies with more limited capabilities but still accomplish the functions as described herein. 
       FIGS. 7-14  describe the exemplary program objects that are utilized in connection with PPC communication with RECC devices and CES operators. Specifically  FIG. 7  describes the New Estimate object which contains the records including estimate or repair order identification number and the name of the entity that is requesting the pricing associated with the parts needed for the particular damaged vehicle. 
       FIG. 8  describes the Estimate Header object. This object contains records with all the data fields for the exemplary PPC to provide a price for the indicated repair parts. As shown in  FIGS. 8 and 8A , such information commonly includes information which uniquely identifies the vehicle including the model year, make, model manufacturer associated therewith. The data also includes an identifier for the company responsible for payment, the vehicle mileage and the state where the vehicle is located. As will be explained in greater detail later, this information is utilized by the pricing logic in order to provide parts pricing for OE parts to include in the parts pricing record (PPR) produced by the PPC. 
       FIG. 9  shows the Part object which includes the request and response records for the pricing for one or more OE parts associated with a collision situation and PPR record. The values associated with the object are described in the indicated figures. 
       FIG. 10  shows the information included in the Part object. This data includes record data which identifies the OE part and the quantity needed in connection with the vehicle repair situation. It should be mentioned in connection with the Part object that in some situations, the collision estimating system software operated by an RECC will also attempt to calculate part price data. When such data is provided, it will be included in the Part object data. 
       FIG. 11  shows the data in the Related Part object. The Related Part object has to do with data records concerning an aftermarket or used part that may be included in the NPR data that is submitted to the PPC. As previously mentioned, the exemplary PPC includes the non-OE part (or N-part data) in the PPR record data that is stored by the PPC as it may be used in some cases to offer a vehicle repair entity. The opportunity to purchase a new OE part at the same price as an N-part. 
       FIG. 12  shows the Quotes object of the exemplary embodiment. This object corresponds to the list of parts in a given estimate or PPR record. 
       FIG. 13  describes the EMS Data object. The EMS Data object contains a record including a complete data set of information related to the damaged vehicle, an example of which is shown for example in  FIG. 20 . This is also referred to herein as the parts pricing record for PPR data. 
       FIG. 14  describes the Errors object which indicates records of errors or anomalies that may occur in connection with operation of the PPC. 
       FIG. 15  describes the methods that are invoked in connection with the operation of the PPC and the program objects previously described.  FIG. 15  lists the methods, how they are used and the data each returns. These API method endpoints described in  FIG. 15  enable the collision estimating system instructions and functions operated in RECC systems to create parts pricing records, store them in the PPC and retrieve them as desired.  FIG. 16  describes an exemplary session for communications and logic flow carried out between an RECC used for creating a parts pricing record (PPR) associated with a damaged vehicle, and the PPC which provides the pricing data for use in connection with the estimate/repair order. 
       FIG. 16  describes the communications and the functions carried out in producing a parts pricing record PPR which is alternatively referred to in the drawings as an EMS data set. As shown in  FIG. 16 , the communications and logic flow create a parts pricing record which includes the prices for the OE parts that are specified by the RECC as needed for repair of the vehicle. Further in the exemplary communications and logic flow, the RECC is enabled to access and update the parts pricing record and EMS data set data that is stored in the PPC. 
       FIGS. 17-22  describe the methods that are carried out in connection with communications between the RECC and PPC and the logic flow described in  FIG. 16 . Examples of the data that is included in the request to the method and the results provided by the method are also included in the Figures. The Figures also describe the resource URLs for the methods described in the exemplary arrangement of the PPC. Other information such as the need for authentication to access the method and whether the method is rate limited is also described. In some cases, the method may have the rate selectively limited through operation of the control logic which limits the number of requests which can be processed within a given time period based on the type of authorized user of the PPC. 
       FIG. 17  describes the POST/estimates method which is used to create the estimate and returns a newly created estimate ID in the PPC system. 
       FIG. 18  describes the POST/estimates/{id}/parts method. This method is used to retrieve the parts prices of OE parts. The example shows the information that is submitted concerning the damaged vehicle and the part numbers and the returned pricing data for the PPR based on the pricing logic. 
       FIG. 19  describes the method associated with the POST/estimates/{id}/quotes method. This method creates a quote with the final list of parts for the estimate or repair order record. It returns the newly created quote ID. This method includes pricing for both OE parts and non-OE parts. 
       FIG. 20  describes the POST/estimates/{id}/EMS data method. This method submits a complete EMS data set associated with a parts pricing record. The submitted information includes all the EMS data described in the Figures. However, as indicated some of the data may not be available and need not be included or may be filled with null values. The method produces a result that indicates the data ID. 
       FIG. 21  describes the PUT/estimates/{id}/quotes/{quoteld} method. This method is used to update an existing quote by replacing parts in the PPR with a new list of parts. An example is indicated and the method returns an indication of success if the method is successfully carried out. 
       FIG. 22  describes the PUT/estimates/{id}/EMS data/{ems Datald} method. This method is used to replace the entire data set in a PPR with a new EMS data set. Again as previously mentioned, EMS data sets include information that is not related to parts pricing and which in some cases may be omitted or filled with null values. The method is used to replace an existing PPR data set and returns an indication of success if the data is updated. 
     The exemplary PPC further includes the capability for delivering large numbers of PPR records responsive to needed parts record (NPR) data for a large number of damaged vehicles. In the exemplary arrangement the PPC is enabled to accept batches of EMS data in compressed data files. As described in  FIG. 23 , the compressed data files include contents for each record in the j son format. These large batch files are then processed through the operation of the exemplary PPC to provide parts pricing data in a folder that can be accessed by the submitting entity. Further, as is the case with individually processed files, each of the NPR files is operative to cause the PPC to produce a PPR/EMS file data set that is stored in the PPC data store. 
     Thus as can be appreciated, the exemplary PPC is enabled to provide pricing for OE parts to external RECC systems and store records that correspond to each damaged vehicle situation. Further the RECC systems are enabled to access and update the PPR data records for purposes of producing estimates/repair order records. 
     The exemplary PPC further enables communication with numerous auto dealer parts order circuit (ADPOC) devices. As previously described, the exemplary ADPOC devices are enabled to access the PPR data and EMS data sets in connection with the dealer receiving an order for the OE repair parts from a VRE circuit associated with a vehicle repair entity (VRE) responsible for repairing the damaged vehicle. Further the exemplary PPC provides additional capabilities to the dealer through the ADPOC which enables the dealer to offer the VRE the capability to acquire OE parts on terms that are competitive with aftermarket and used parts in many circumstances. Further the exemplary PPC and its capabilities to communicate in a data format that can be read and used by numerous different computer program languages enables various different types of ADPOC platforms running different ADPOC programs and dealer management systems (DMS) instructions to readily communicate with the PPC. 
     The communications and functions of the exemplary PPC in connection with an ADPOC is described in connection with  FIGS. 24 through 35 .  FIG. 24  describes schematically the communicating and logic flow associated with enabling authorized users to access PPR records stored in the system. As was previously described in connection with RECC access, ADPOC access relies on an implementation of OAUTH 2.0 in which the ADPOC operator is provided a client ID and client secret when they are initially granted authorization to utilize the PPC by the operator thereof, which operator in this case is referred to as OEC. As is the case with RECC systems, ADPOC systems are issued an access token which limits access to PPR files that include OE parts of the type sold by the dealer. Further the access token has a limited duration and must be refreshed after the assigned period of time. 
     In the exemplary arrangement the PPC in interacting with ADPOC systems will carry out functions associated with the four indicated program objects listed in  FIG. 25 . These four objects are described as the Quotes, Parts, Invoices and Errors Objects. 
       FIG. 26  describes the methods that are carried out by the objects in response to the external ADPOC/DMS applications.  FIG. 26  lists the methods and the usage thereof. It also describes the returns and endpoints of each of the methods. 
       FIG. 27  describes in detail the particular implementation of the PPC in communicating with an ADPOC in order to retrieve the authorized and desired PPR records for purposes of placing an order for the OE parts described therein.  FIG. 27  further describes the communications carried out in sessions associated with the ADPOC system operating to receive the order associated with the OE parts that are included in a PPR record. In the exemplary system the flow represented in  FIG. 27  initially describes a scenario in which a dealer operates their ADPOC dealer management system (DMS) to create parts quotes in the designated dealer portal operated by OEConnection, which is also the operator of the PPC in the exemplary embodiment. This step can be utilized in some embodiments to create DMS quotes associated with the particular parts which are included in PPR/EMS data sets. This particular step is useful in the exemplary arrangement as this enables the ADPOC of the dealer that accesses a particular PPR to have not only the pricing data that was given by the PPC for purposes of creating the estimate/repair order record, but also other pricing data for the OE parts. Such other pricing data includes for example, the dealer price data for the particular part and any rebates or other incentives that the manufacturer offers in connection with the dealer&#39;s sale of the particular part. Other pricing data which is provided in an exemplary embodiment includes the trade price data which represents pricing that is offered to other entities engaged in the trade, such as the body shop operators. The difference between the quoted parts price in the PPR for the part and the trade price which the VRE will actually pay enables the VRE to make a profit on the sale of the parts to the owner of the vehicle in connection with making repairs. Further as discussed in additional detail later, the interconnection with pricing capabilities of the dealer portal may facilitate enabling the dealer to sell an OE part where an aftermarket or used part had been originally specified in the PPR. Further as later explained, exemplary arrangements enable the ADPOC to operate to submit the order as well as to process manufacturer requests for rebates associated with the sale of the particular OE parts. 
     As represented in  FIG. 27 , the exemplary transaction flow enables the ADPOC/DMS system to obtain the PPR data, to update it as necessary, and to also when the order for the parts is placed with the dealer, to remove it from the list of available PPR records for which dealers can fulfill the parts orders. 
       FIG. 28  describes the Quotes object of the PPC. As shown the Quotes object provides a response to the request for pricing for OE parts in a collision transaction. 
       FIG. 29  shows the Parts object which shows the part and pricing data in a quote that a dealership provides concerning the price of a part. 
       FIG. 30  describes the Invoices object. The Invoices object provides a list of parts tied to a quote that have been invoiced in an ADPOC/DMS. 
       FIG. 31  describe the Errors Object which provides the reasons that a request to obtain a quote is invalid or rejected. 
       FIGS. 32-35  describe the methods that are carried out in connection with the PPC ADPOC transaction flows. 
       FIG. 32  describes the GET/invoices/quotes method. This method is used to retrieve a collection of records corresponding to open quotes. The method supports a number of different query parameters by which existing PPRs/EMS data sets can be selected and retrieved. Examples of ways in which the PPRs are retrieved using the method are shown. Thus for example a dealer operating an ADPOC who is contacted by a VRE about parts needed for repairing a vehicle, may recover the PPR data in the PPC data stores using any of the query parameters that the VRE may provide. 
       FIG. 33  in contrast describes the GET/invoices/quotes/{id} method. This method provides for retrieval of a single PPR by the associated id. Thus if the dealer has the particular id, the PPR/EMS data set can be retrieved using the id. 
       FIG. 34  describes the GET/invoices/quotes/{id}/parts method. This method is used to retrieve identifying data describing all parts associated with a PPR. As shown in  FIG. 34 , this method provides as a result, a record including the number, description, quantity and pricing information associated with each part. Further in the exemplary embodiment the pricing information includes the list price included in the estimate, the cost to purchase the item and the trade price offered to a body shop or other dealer. 
       FIG. 35  describes the POST/invoices method. This method operates to update the PPC with the DMS invoice information. This information is used to indicate that the ADPOC has been operated to order the particular parts for a VRE, and/or that one or more fulfillment records have been generated. 
     Thus as can be appreciated, the exemplary PPC enables ADPOC systems to be operated to retrieve PPR records and to enable the dealer to fulfill the order of a VRE for the OE repair parts included in a PPR record associated with a damaged vehicle. 
     The exemplary embodiment of the PPC enables calculating the quoted price for repair parts of different types that may be requested for purposes of repairing a damaged vehicle. The exemplary PPC also executes programmed instructions which implement discount logic for purposes of determining the quoted price for a given part. 
       FIG. 36  lists exemplary categories of collision parts for which situational pricing is offered through operation of the exemplary PPC. As can be appreciated, these different parts have widely different properties and have different levels of demand. These factors impact how the vehicle manufacturer charges for such items. Further the cost to make such items can vary widely. For example, certain parts require a substantial tooling investment where other parts do not. The manufacturer&#39;s dealer price generally reflects these different considerations. 
       FIG. 37  lists factors that influence the quoted parts prices offered by the exemplary PPC. These quoted parts prices are the situational pricing that an entity operating an RECC such as a repair shop or an insurance company, receives in response to their request for pricing. As represented in  FIG. 37 , the exemplary pricing logic considers the dealer prices set by the manufacturer. Also considered is whether the particular part is covered by patent protection. This factor could be important as aftermarket parts corresponding to a patented part will not be available. Other considerations include filtering whether the particular type of part for which pricing is being requested falls into one of the product lines, such as those indicated in  FIG. 36 . 
     Exemplary situational pricing also considers information specific to the vehicle repair that needs to be made. Factors that are considered by the pricing logic include the company who is responsible for making payment for the repairs. Other considerations include the model year, manufacturer, make, model and mileage of the vehicle. These factors are important because often companies or other persons responsible for repair do not accept the use of aftermarket and/or used parts on what are considered relatively new and/or high end vehicles. Alternatively if a vehicle is older or has high mileage or is not considered a high end vehicle, aftermarket or used parts may be considered acceptable. 
     Other factors considered by the pricing logic include the residence state of the vehicle owner. This factor may have a bearing on different aspects of pricing engine logic. The state in which the vehicle is located may have rules that regulate the use of aftermarket or used parts so this can impact the requirement to use OE parts. In addition the state of the vehicle has a bearing on the level of competition which factors into the price. 
     Another factor in pricing is whether the part specified is an OE part or non-OE part. This includes used parts and aftermarket parts. As discussed previously, the exemplary PPC provides special processing instructions for dealing with N-parts to provide opportunities to enable the dealer to substitute a sale of an OE part that the dealer provides for the N-parts which were originally specified for use in repair of the vehicle. 
     Other factors considered by the exemplary pricing logic include the historical pricing to meet competition. Data included in the files of the exemplary PPC include the lowest selling price of each particular part on a national basis and the lowest selling price of the part on a state basis. These factors are utilized in making decisions when attempting to provide attractive pricing for OE parts to compete effectively with N-parts. 
       FIG. 38  is similar to  FIG. 37  and shows where in the exemplary embodiment of the PPC, the sources from which the data in each of the factor categories is derived. As reflected in  FIG. 38 , the categories of information regarding particular parts come from the vehicle manufacturer who supplies the parts. Companies such as insurers may have their own rules and policies which are stored in the records of the PPC concerning whether aftermarket or used parts are allowed to be used on particular vehicles. Also, manufacturers may provide discounts based on the year, make and model of the vehicle. This may be done for a number of reasons including parts availability for models in given categories. Further in exemplary arrangements, records include rules or other program requirements associated with particular states and the parts that can be used. The exemplary PPC also includes files which store lowest selling price information for each particular part on both a state and national basis for use in calculations of discounts. 
       FIG. 39  shows graphically some different approaches that can be used in connection with an exemplary embodiment of the PPC for purposes of creating the estimate/repair order which includes the price for repair parts. The use case on the left which is referred to as a collision estimating system integration, represents a situation where the RECC is operated to work automatically with the PPC. The RECC provides an NPR including the list of parts that are needed to the PPC and obtains the parts pricing automatically in connection with the parts pricing record. 
     The use case displayed in the middle involves a scenario where estimates are imported from the CollisionLink system offered by OEConnection. This approach involves routing back the file to the entity&#39;s collision estimating system. In this case the PPC produces the prices based on the imported estimates. 
     The use case shown on the right shows a manual input of each part number into the PPC system and the pasting of pricing into the shop&#39;s collision estimating system. This approach requires the most manual labor. However, it should be understood that all of these approaches are effective and readily accomplished compared to other approaches that can be carried out without the functions provided through operation of the exemplary PPC. 
       FIG. 40  represents schematically the work flow carried out by a dealer in connection with quoting, ordering and processing requests for manufacturer&#39;s rebate on collision parts sold by the dealer. As shown in  FIG. 40 , this process generally involves three separate processes carried out by the dealer. These processes include viewing the PPR records of the pricing, and recording the sales price for the parts to the VRE who is requesting to purchase them from the dealer. The second step includes creating an invoice in the dealer management system (DMS) which includes the list price and the sales price. The third step is to submit a claim for the reimbursement that the vehicle manufacturer provides on the sale of the manufacturer&#39;s OE parts. 
       FIG. 41  reflects different options for viewing the list price in the PPR and quoting sales price by the dealer. The approach referred to as method A, involves a situation where a dealer uses the ADPOC to obtain prices via the CollisionLink order system. This is a system offered by OEConnection that provides a way for a dealer to acquire needed repair parts and to make repair parts the dealer has in inventory available to others.  FIG. 42  shows an exemplary output display screen which shows an output produced on the display of the ADPOC through operation thereof in response to the PPC in response to a look up request. As highlighted in this example, the output provided by the PPC includes the parts and the list prices that the PPC has provided to the company responsible for payment or other entity that requested pricing. The PPC is also operative to provide to the ADPOC the trade price which reflects the price of each part recommended to be charged when the dealer sells such part to a body shop or other entity engaged in the repair business. The display also provides to the dealer the list price for the particular part. 
     Referring again to  FIG. 41 , the method described in the middle includes the approach of looking up a PPR in the PPC data store as represented in  FIG. 43 . This approach to recovering PPR data from the PPC enables the dealer through the ADPOC to review the quote details. This includes both the OE parts which have been included as part of the quote. In the exemplary arrangement, the PPC provides a segregated list of the non-OE parts that have also been specified for use in carrying out the repair. The PPC is operative to calculate responsive to its pricing logic the pricing that can be made available by the manufacturer to offer a price on a corresponding OE part that can be used instead of the specified recycled or aftermarket part which is at least as low as that offered for the used or aftermarket part. The exemplary arrangement further indicates the reimbursement that is offered to the dealer in the event that they sell the OE part in place of the used or aftermarket part specified. In the exemplary arrangement the PPC operates to determine if there is an opportunity to lower the price of the corresponding OE part so that it is more attractive to the VRE making the repairs than specified N-part. This enables the dealer selling the OE parts that have already been specified to have the opportunity to try to convert the VRE buyer to buying OE parts instead of the N-parts. Further as represented in  FIG. 44 , the quote look up functionality of the PPC enables the dealer to search for quotes within the system to find the particular PPR quote or quotes for the vehicles that are being repaired by the VRE who may approach the dealer about supplying the needed repair parts. 
     Referring again to  FIG. 41 , the method on the right enables the dealer to operate the PPC in conjunction with the live lookup. As represented in  FIG. 45 , in this exemplary system the PPC operates in conjunction with the CollisionLink system to provide pricing outputs concerning the repair parts of interest to the dealer. Likewise similar to the previously described embodiment, any N-parts which have been specified are segregated and information on suitable OE parts and additional discounting is offered to provide the dealer with an opportunity to sell the VRE additional OE parts at prices that meet the prices offered for the aftermarket or used parts. Of course it should be understood that these approaches and screen outputs that are provided to the dealer are exemplary and in other arrangements, other approaches may be used. 
       FIG. 46  graphically describes the step associated with creating an exemplary invoice in the dealer management system (DMS) which includes the list and sales prices. As represented by the left-hand option shown in  FIG. 46 , one approach is to manually input the parts and pricing data produced by the PPC to the ADPOC and the DMS application operating therein. An alternative streamlined approach is represented on the right in  FIG. 46 . The streamlined approach enables the export of pricing data from the PPC stored information. This approach enables automatically integrating the pricing data into a quote produced by the DMS application. This automated export approach is carried out through additional functions that are available in conjunction with the CollisionLink service that is offered by OEConnection. 
       FIG. 47  is an alternative schematic view which represents the record data export capability that can be automatically carried out through the combined operational capabilities of the PPC, the DMS application operated by the dealer of the ADPOC, and the CollisionLink service. These capabilities enable the dealer to produce a quote from their system for selling the parts without the need for manual data inputs. 
     As previously discussed, in exemplary approaches vehicle manufacturers offer rebates to dealers in connection with the sale of OE parts. These rebates may increase in cases where the dealer is encouraged to drop the price of the part so as to make a sale of an OE part that replaces a specified aftermarket or used part. 
       FIG. 48  shows schematically the processes carried out for submitting a claim for reimbursement by the dealer to the vehicle manufacturer in connection with the sales of OE parts. As represented on the left in  FIG. 48 , the exemplary embodiment of the PPC enables the dealer to manually input the information from their ADPOC concerning the order into the PPC, and select to submit the claim for reimbursement to the manufacturer through operation of the PPC. The PPC operates in accordance with its programming to submit the claim for reimbursement of the dealer to the vehicle manufacturer. 
     Alternatively as represented on the right in  FIG. 48 , manual aspects of this process can be automated. In the exemplary arrangement the automation process offered by the CollisionLink service of OEConnection enables automatically importing the record claim details from the ADPOC and the dealer management system application, to the PPC. Once the data has been automatically imported, the dealer may select to present the claim. This streamlined method for importing the invoice data is further represented in  FIG. 49 . The exemplary PPC is configured to accept the data automatically and import it into the proper fields within the reimbursement claim application. This readily enables the dealer to submit their claim associated with part sales to the manufacturer. 
       FIGS. 50-52  describe the logic carried out by the exemplary embodiment of the PPC in connection with providing prices for OE parts to the dealer in an effort to have the dealer be able to effectively compete on price with aftermarket parts or used parts that may be designated for use in connection with the repair of a particular vehicle. As represented in  FIG. 50 , in the exemplary PPC pricing for OE parts to substitute for N-parts can be requested via a look up. As discussed previously, such a look up may be conducted via inputs to an ADPOC system or other suitable system operated by the dealer. However, as represented at the bottom of  FIG. 50  when a look up of pricing for an OE part is conducted, when there is no existing parts pricing record (PPR), the pricing provided for the OE part will be based on the pricing logic for pricing the parts. It will not include the pricing logic to beat a lower price that may be associated with an N-part in an existing PPR record. However, as indicated on the right in  FIG. 50 , where there is existing PPR records which include N-parts for which OE parts can be substituted, the pricing logic in the exemplary PPC may operate to provide a lower competitor price for the OE part. 
       FIG. 51  describes the PPC pricing logic in cases where there is not a pre-existing PPR data record stored in the system. In this case to calculate the pricing of the OE part, the system checks the state and national files for the pricing associated with the part. If the part&#39;s pricing is not at the lowest selling price in either file, a default dealer price is offered which is a set percentage discount off the listed dealer price. As represented in  FIG. 51A , step two of the logic considers whether the vehicle&#39;s age and mileage fall within the payor company&#39;s threshold for requiring OE parts. If the company responsible for payment requires OE parts under its rules, there is no reason to further discount the OE part because no substitute N-parts may be provided. A third step in the logic is to resolve the state of the vehicle owner and apply any rules associated with that state discount. The final step is to add the age/mileage discount and state discount and to calculate the proposed price. This proposed price is then compared to the lowest price at which the OE part has been offered. If the calculation results in a price lower than the lowest allowable price, the lowest allowable price is offered. If not, the calculated discount is what is used. Generally this approach will result in a price for the OE part that is at or below the N-part which could be specified for use in connection with the repair of the particular vehicle. 
       FIG. 52  describes the exemplary logic when there is an existing PPR record which includes an N-part. This approach involves checking the lowest allowed PPC price that is allowed, similar to the price from the prior approach. However, in this case, the second step involves comparing the calculated discount price to the N-part price included in the PPR. The pricing logic associated with the PPC then operates to match the price for the N-part or offer the lowest available price. Of course as previously discussed, in exemplary arrangements when the PPC operates to lower the price, the reimbursement to the dealer is increased so that the dealer maintains a reasonable profit margin. 
     The result of applying these approaches is to enable the dealer to sell the VRE responsible for repairing the vehicle the higher quality OE parts at the same or a lower price than the VRE would pay to acquire aftermarket or used parts. In this way, the VRE can avoid the possible additional labor and work that may result from having to make a non-OE part that will work satisfactorily in connection with the repair of the vehicle. In addition, the vehicle owner generally gets a higher quality of repairs by having OE parts that are the same as were installed when the vehicle was new. 
     It should be understood that the approaches described in connection with exemplary PPC and related devices may be supplemented to add additional functions and capabilities to further enhance the procurement of repair parts. Such additional features may include, for example, the automated tracking of the dispatch and delivery of the repair parts, the staging of deliveries for selected items or parts and provisions for assuring that OE parts that come from different locations are coordinated to arrive at the VRE before the time that they are needed in conjunction with particular repair work that needs to be done on the vehicle. These and other capabilities to facilitate repair of damaged vehicles and the parts associated therewith provide significant advantages for the repair of damaged vehicles. 
     An alternative arrangement which may be utilized in some embodiments for the supply of vehicle repair parts is represented in  FIGS. 53-60 . Such a system may be utilized by a VRE or other parts purchaser to acquire the parts listed in a repair order record or that are otherwise needed for repair of a damaged vehicle. In some arrangements the exemplary system may be used to acquire a plurality of parts such as would be included in the repair order record, or subsets of parts or individual parts that may be needed for such repairs. 
     With reference to  FIG. 53 , an exemplary system  101  that facilitates automatically routing an order for a repair part to a plurality of different suppliers at different points in time is illustrated. In an exemplary embodiment, the system  101  may be resident upon server circuitry that is accessible by way of one or more networks including the Internet. For instance, a parts purchaser can access the system  101  through a VRE circuit or other device by utilization of a web browser by directing such web browser to a particular web page. Furthermore, a part supplier can access the system  101  by way of circuitry which is operative to access a web page or which executes instructions included in a client side application that is in communication with the system  101 . 
     The system  101  comprises receiver component circuitry  103  that receives an order from circuitry such as a VRE circuit associated with a parts purchasing user  104 . The received order can include a single vehicle repair part or a plurality of repair parts. In an example, the user  104  can utilize a VRE circuit to access a web page through utilization of a web browser and may select one or more parts for purchase that are described on such web page. Additionally, the user  104  can select a particular parts provider (a first provider) that is the preferred provider for the user  104 . For instance, the first provider  106  can be a provider that is relatively proximate geographically to the user  104 . The order placed by the user  104  can have various attributes corresponding thereto. An exemplary attribute includes a manner in which the part in the order is to be provided to the user  104  (e.g., by way of a particular shipper, through the user picking up the order at the location of the provider, the provider dropping off the ordered part(s) to the user  104 , etc). Another exemplary attribute can be a type of account utilized by the user  104  to purchase the parts in the order. Account types can include credit card, debit card, line of credit, etc. Still yet another exemplary attribute corresponding to the order may be a type corresponding to the user  104 . For instance, the user  104  may be an individual that is purchasing products in the order for personal use. In another example, the user  104  may be a VRE business that is purchasing the products in order for resale to the owner of a damaged vehicle. 
     Rules analyzer circuitry  108  is in communication with the receiver circuitry  102  and operates to analyze attributes of the order and the user  104 . Based at least in part upon this analysis, the rules analyzer circuitry  108  can ascertain whether the order of the user  104  qualifies for automated order routing. 
     Specifically, the system  101  can comprise a data store  110  in operative connection with the rules analyzer circuitry  108  that includes circuit executable instructions including a plurality of rules  112 . For instance, a first rule in the rules  112  can indicate that an order only qualifies for automated order routing if the user  104  is an end user that is utilizing the products in the order for personal use. Another exemplary rule included in the rules  112  may indicate that the order qualifies for automated routing only if the user  104  is paying by way of a credit card or debit card. Still yet another exemplary rule that can be included in the rules  112  can indicate that the order only qualifies for automated routing if a particular type of shipping has been selected by the user  104 . For instance, an order of a product cannot be routed to another provider if the user  104  has agreed to pick up the product from the first provider  106 . Yet another exemplary rule that can be considered by the rules analyzer circuitry  108  is to insure that the price for the products in the order of the user  104  cause any of the available providers to achieve a gross profit margin of a threshold percentage (e.g., 17 percent). Other rules may apply to order routing when the user is a VRE or in other acceptable circumstances in which automated order routing may be used. 
     If the rules analyzer circuitry  108  determines that the order is eligible for automated routing, the rules analyzer circuitry  108  can output data to the receiver component circuitry  103  to indicate the availability of automatic routing for such order. The receiver component  103  may then provide the user  104  with data that indicates to the user  104  that automated routing of the order is available to such user  104 . Thereafter, the user  104  can choose whether or not to have the order automatically routed if the first provider  106  does not commit to fulfilling the order of the user  104  in a timely manner. If the user  104  chooses to have the order automatically routed, the user  104  can indicate to the receiver component circuitry  103  such choice and can finalize the order. Upon the user  104  finalizing the order for an agreed upon price, the receiver component circuitry  103  can transmit a confirmation to the user  104  pertaining to the order. This confirmation can indicate to the user  104  that the order placed by the user  104  will be fulfilled by a provider for the agreed upon price. Moreover, at the time the order has been finalized, an authorization for the agreed upon price can be placed on the credit card or other account (e.g. PayPal account, stored value account, debit card account, etc.) of the user  104  by or on behalf of the first provider  106 . 
     The system  101  further comprises router component circuitry  114  that, upon receiving an indication from either the receiver component  103  or the rules analyzer circuitry  108  that the order has been placed by the user  104 , can route the order to the first provider  106 . As described above, the first provider  106  can be selected by the user  104  as the preferred provider for the user  104 . The data corresponding to the order transmitted to the provider  106  can include information such as the identity of the user  104 , repair parts included in the order and prices for such parts. The system  101  further comprises circuitry that comprises a clock function which is alternatively referred to herein clock  116 , wherein the router component circuitry  114  initializes the clock  116  upon transmitting the order to the first provider  106 . Additionally a time value pertaining to the clock  116  can be output through a display associated with circuitry operated by the first provider  106 . In an exemplary arrangement the time value together with the order parts indicates to the first provider  106  that the first provider  106  has the exclusive right to commit to fulfilling the order within a certain amount of time before the order is routed to other providers. In exemplary arrangements the circuitry operated by the parts provider may include a DMS, inventory management or other computer system operated by the provider. The provider may provide one or inputs through an input device of the system operated by the provider to commit to fulfilling the order. Such inputs from the provider cause one or messages to the router component circuitry or other order routing circuitry indicating the commitment of the provider. 
     The router component circuitry  114  can monitor values output by the clock  116  to ascertain if a first threshold amount of time has passed without the first provider  106  committing to fulfilling the order by the user  104 . If the first provider  106  commits to fulfilling the order prior to the passage of a threshold amount of time, then the first provider  106  can fulfill such order. Order finalizer component circuitry  118  can finalize the order of the user  104  and can output a detailed order confirmation to such user  104 . This order confirmation can include one or more records that identify the first provider  106 , the repair parts, and the agreed upon price, etc. The components  103 ,  108 ,  110 ,  114 ,  116  and  118  may alternatively be collectively and individually referred to as order routing circuitry. 
     If the first threshold amount of time has passed and the first provider  106  has not responded with one or more messages indicating that the provider has committed to fulfilling the order of the user  104 , then the router component circuitry operates in accordance with its executable instructions to  114  route one or more messages corresponding to the order to at least one of a plurality of remote circuitry corresponding to systems operated by other parts providers  120 - 122 . At the time of such routing, the router component circuitry  114  can also transmit data to the circuitry of the provider  106  to indicate to the provider  106  that the order is no longer exclusive to the first provider  106 , and that at least one other provider is now able to commit to fulfilling such order. For example, messages from the order routing circuitry may cause graphical indicia to be provided by application instructions executing on the system circuitry of the provider  106  to inform the provider  106  that the order may be committed to be fulfilled by other providers. Such outputs may be provided through a display or other output device. 
     After passage of the first threshold amount of time, the router component circuitry  114  can be in communication with the rules analyzer circuitry  108  in connection with determining which of the system circuitry associated with providers  120 - 122  are to receive the order. The rules analyzer circuitry  108  operates responsive to the rules  112  and in exemplary arrangements applies such rules with various attributes pertaining to the order, the user  104 , the parts and/or the providers  120 - 122  to determine which of the providers is to be selected to receive the order of the user  104 . 
     An exemplary rule that can be included in the rules  112  may require that the provider to which the order is to be routed, currently has the part or parts included in the order in inventory. The data store  110  may include inventory data  124  and the rules analyzer circuitry  108  can check the inventory data  124  associated with each of the providers  120 - 122 . The data store  110  can further comprise data corresponding to provider attributes  126 , and the rules analyzer circuitry  108  can analyze the provider attributes  126  in connection with applying the rules  112  when selecting providers for order routing. These provider attributes  126  can include data such as business sizes of the providers  120 - 122 , geographic locations of the providers  120 - 122 , user ratings given to the providers  120 - 122  (previous responsiveness to orders from purchasers from the providers  120 - 122 ), classifications of the providers  120 - 122 , types or brands of products carried by the providers  120 - 122 , and other data. Thus, in some arrangements exemplary rules pertaining to which of the providers  120 - 122  to select for routing the order of the user  104  can include a rule that requires a provider to be within a certain distance of a geographic location of the user  104 . Another exemplary rule can require that the provider have a particular rating from prior purchasers who have given feedback data regarding the provider. Yet another exemplary rule can require that the provider be of a particular size or classification, or have other attributes. Further the system circuitry may apply different rules, depending on whether the user is an individual, a VRE or other category of user. 
     Subsequent to the router component circuitry  114  routing the order of the user  104  to the system circuitry of providers  120 - 122 , one or more of such providers  120 - 122  can commit to fulfilling such order. That is, a provider that commits to fulfilling the order will provide the parts to the user  104  in exchange for payment from the user. In such a case, where the first provider  106  does not end up committing to fulfill the order, the order finalizer component circuitry  118  operates to cause the authorization placed on the credit card or other user account by or on behalf of the first provider  106 , to be released. Thereafter, the order finalizer component circuitry  118  can place a different authorization on the credit card or other account of the user  104  on behalf of or by the provider that ended up committing to fulfilling the order. Thereafter, the order finalizer component circuitry  118  can cause one or more electronic messages to be transmitted to the system circuitry associated with the user  104  to indicate details pertaining to the purchase of the parts, including the identity of the provider that committed to the order, an estimated time of arrival of the parts to the user  104 , an amount of sales tax for the product, and other transaction details. 
     It should be understood that there may be some situations where neither the first provider  106  nor the providers that were routed the order after the first threshold amount of time passed, may commit to fulfilling the order of the user  104 . Thus, the router component circuitry  114  of the order routing circuitry can operate to monitor a time period or value of the clock  116  to determine whether such value has passed a second predefined threshold. In an example, the first predefined threshold period may be 30 minutes such that the first provider  106  has the exclusive right to commit to fulfilling the order to the user  104  for 30 minutes. After the expiration of 30 minutes, the router component circuitry  114  can route messages corresponding to the order to the other providers, wherein such providers are selected through operation of analyzer circuitry and utilization of the rules  112  in the data store  110 . The second threshold amount of time may be 15 minutes, such that the first provider  106  and the other provider to which the order has been routed, may have 15 minutes to send one or more messages to the system circuitry indicative of the particular provider&#39;s commitment to fulfilling the order. If this second threshold amount of time passes, the circuitry may operate in accordance with its programming to cause a particular predefined provider, such as a parts wholesaler or manufacturer to automatically commit to fulfilling the order. Accordingly, the user  104  can submit an order with confidence knowing that his or her order will be fulfilled whether by the preferred first provider  106  or by some other provider. Furthermore if the provider  106 ,  120 - 122  are franchises of a particular company, the parent company can have knowledge that a sale to the user  104  will not be lost. Moreover, opportunities to individual franchises to complete sales are not lost. Any lost sales can be attributed to the delay of a provider that has been selected as the preferred provider. 
     While the above examples describe the routing of parts orders in a relatively low number of “waves” (e.g., first to the preferred provider, then to other providers, and then to a default provider such as a wholesaler or manufacturer), it is to be understood that the system  101  can be configures to select providers and route orders in any number of “waves”. For instance, exclusive rights can be given to the first provider  106  for a first threshold amount of time. Thereafter, additional providers can be selected through use of the rules  112 , and the order can be routed to those providers. If none of these providers commits to fulfilling the order, then still more providers can be selected through use of the rules  112 , and the order can be routed to these providers. Thus, the number of “waves” of order routing can be configured as desired by an implementer of the system  101  based on the system circuitry and circuit executable instructions associated therewith. 
     Moreover, an implementer of the system  101  can configure order routing to occur only at certain times of the day. For example, a provider may not be expected to commit to an order at 1:00 a.m. local time. Accordingly, the clock  116  may be initialized and monitored only during times that are configured by the implementer of the system  101 . Accordingly, various configurations of the system  101  can be implemented based on local time parameters as well as parameters related to holidays, weekends and other factors that are implemented in the circuit executable instructions. 
     In an exemplary embodiment, the providers  106  and  120 - 122  may be automobile dealers that are franchises of a particular parent automobile manufacturer. In such an embodiment, the user  104  who is an individual consumer can place an order for an automobile part for an automobile owned or operated by the user  104 . Accordingly, in an example, the user  104  can place an order for a particular automobile part and may select a neighborhood dealership as the preferred automobile dealership. Additionally, the user  104  can agree to choose to have the order automatically routed, so long as the order qualifies for such routing. The local automobile dealership will have the first opportunity to commit to fulfilling the order of the user  104 , and if the automobile dealership commits to fulfilling the order within the threshold amount of time, will make the profit from the sale. If, however, the automobile dealership is lax in monitoring automobile part sales, or otherwise declines to fulfill the order, then other dealerships can be given the opportunity to commit to the order of the user  104 . Further, as mentioned above, an agreed upon price between the user  104  and the first automobile dealership can include a particular threshold amount of profit, such that any dealership that commits to fulfilling the order may make the particular threshold amount of profit. 
     If no dealership commits to fulfilling the order of the user  104  within some threshold period of time mentioned, then the order routing circuitry may operate to cause the automobile manufacturer itself to an commit to fulfilling the order, thereby keeping the user  104  happy with the automobile manufacturer. In another exemplary embodiment, a relatively large dealership may wish to program its DMS circuitry to operate to automatically commit to fulfilling any orders that are not committed to by other dealerships selected by the router component circuitry  114 . This can result in increased profits for the relatively larger dealership. Similar approaches may be implemented for purchases by VREs and for other categories of customers. 
     Of course, the system  101  is not limited to automobile dealerships but can be utilized in connection with any suitable corporate/franchise relationship. Moreover, other online e-commerce systems may benefit from the functionality of such a system. For instance, some online e-commerce companies agree to sell products from individual companies, wherein the ecommerce companies are paid a certain percentage of the total prices of products purchased by buyers from the individual companies. Accordingly, such online retailer can sell products for various companies, wherein such companies are independent but, in certain circumstances, may sell identical goods. In such a case, the buyer can access an e-commerce application and select a product for purchase that is sold by a particular company, wherein such product is sold through the e-commerce application (e.g., www.amazon.com). If the particular company does not commit to fulfilling the order in some threshold period of time, another company can agree to fulfill the order for the price that was agreed upon between the first company and the buyer. Other implementations and business structures utilize the principles described herein may be implemented by persons having skill in the art. 
     Referring now to  FIG. 54 , the functionality order finalizer component circuitry  118  is shown schematically in greater detail. The order finalizer component circuitry includes circuit components that may be comprised of circuit component arrangements and circuit executable instructions. The exemplary order finalizer component circuitry  118  can comprise a price adjuster circuit component  202  that operates to adjust certain portions of a price to ensure that the final price paid by the user  104  for each repair part is the original agreed upon price between the user  104  and the first provider  106 . In an example, the user  104  can select the first provider  106  as the preferred seller, as the first provider  106  is in geographic proximity to the user  104 . Additionally the user  104  can select to have the products shipped by a particular carrier for a certain shipping price. If the first provider  106  does not commit to fulfilling the order and another provider that is further from the user  104  commits to fulfilling the order, the cost of shipping may change. It is desirable, however, that if such cost of shipping increases, the increase in cost is not passed on to the user  104 . Accordingly, the price adjuster circuit component  202  can adjust, for accounting purposes, the price of a part or parts such that the final price of the part is no greater than and generally the same as the agreed upon price between the user  104  and the first provider  106 . In an example, the circuit component  202  may operate to cause the first provider  106  to be charged the difference in shipping price. In another example, so long as an appropriate amount of profit is made by the provider that commits to fulfilling the order, the circuit component may operate to cause the provider that committed to filling the order to bear the additional cost of shipping. In yet another example, the circuit component may operate such that a manufacturer of the parts can bear the change in shipping cost. 
     Further, in some arrangements the first provider  106  selected as the preferred seller by the user  104  may be in a state that has a first sales tax rate (on sales of a type where sales tax is applicable). Accordingly, the agreed upon price between the user  104  and the first provider  106  can have at least two portions: an original price of the part without considering sales tax, and an amount of sales tax that is to be charged to the user  104  in connection with the sale or the part. If the order, however, is routed by the router component circuitry  114  to another provider in a different state, such state may charge a different amount of sales tax for the purchase of the part. For instance, a provider that commits to fulfilling the order may be in a second state that has a second sales tax rate, which may be higher than the first sales tax rate. In such a situation, the price adjuster circuit component  202  can adjust the non-tax or tax-free portion of the price such that the new combination of the non-tax or tax-free portion of the price plus applicable sales tax is equivalent to the previous total price for the part. For instance, if the user  104  agrees to pay a total of $20 for a repair part from the first provider that is subject to the first sales tax rate, the user  104  will pay $20 for the part from the second provider that is subjected to the second sales tax rate, even though the sales tax rates are different. The system circuitry may operate in accordance with executable instructions in the data store  110  to cause the loss of profits caused by the additional sales tax to be paid by the first provider, for instance, that fails to commit to fulfilling the order in a timely fashion, can be borne by the second provider that fulfills the order so long as a threshold amount of profit is made by the second provider, or can be borne by a manufacturer or other entity that is a parent company or otherwise affiliated with both providers. 
     The order finalizer component circuitry  118  can further include a confirmation circuit component  204  that is configured to transmit an electronic message to the user  104  that confirms that the order has been committed to by a provider. Accordingly, the confirmation circuit component  204  can generate an e-mail, a text message, an automated voice message or other suitable electronic communication, wherein such electronic message can include an identity of the provider that committed to fulfilling the order, a price to be paid by the user  104  for the order, an estimated time of arrival of the part(s) in the order to the user  104 , and other order fulfillment data. 
     The order finalizer component circuitry  118  can also include a reporter circuit component  206  that can generate reports to suitable circuitry operated by a parent company, or other similar entity, wherein the reports can indicate provider performance with respect to committing to orders submitted by users. For example, a parent company may desire that its franchises timely commit to fulfilling orders to keep users relatively happy. The reporter circuit component  206  may, for instance, generate reports that indicate that a particular provider is not timely committing to fulfilling orders. Additionally, the reporter circuit component  206  can generate reports to managers showing that certain departments or other fulfillment entities are not committing to fulfilling orders in a timely manner. Of course these approaches are exemplary and in other embodiments other approaches may be used. 
     With reference now to  FIGS. 55-56 , an exemplary logic flow methodology is schematically illustrated and described that is carried out by exemplary system circuitry. While the exemplary logic flow is described as being a series of steps that are executed in a sequence, it is to be understood that the logic flow is not limited by the order of the sequence. For instance, some steps may occur in a different order than what is described herein. In addition, a step may occur concurrently with another step. Furthermore, in some instances, not all steps may be required to implement the functionality described herein. 
     Moreover, the steps described herein may be carried out responsive to circuit executable instructions that can be implemented by one or more circuits and/or stored on a machine-readable medium or media. The circuit executable instructions may include routines, sub-routines, programs, a thread of execution, and/or the like. Still further, results of acts of the logic flow may be stored in a machine-readable medium, displayed on a display device, and/or the like. The machine-readable medium may be a non-transitory medium, such as solid state, memory, hard drive, ROM, RAM, CD, DVD, flash drive, or other suitable medium. 
     Referring now to  FIG. 55  an exemplary logic flow  300  that facilitates automatically routing a repair parts order from a user is illustrated. The logic flow  300  begins at a step  302 , and at step  304  an order from a user for a part from a first provider for an agreed upon price is received. As described above, the user may select a preferred (first) provider, may select a part or parts that are offered for sale by the first provider, and may agree to purchase the part for a particular price. At this time, for instance, an authorization for the agreed upon price can be placed on a credit card account or other account of the user by or on behalf of the first provider. 
     At a step  306 , a determination is made regarding whether or not the order is routable to other providers. A variety of attributes can be taken into consideration by the system circuitry when determining whether or not the order is routable. These attributes can include a type of user (whether the user is an end user consumer, a VRE, or other type business), a type of payment that is going to be employed by the user to purchase parts in the order, whether one or more parts in the order are on backorder, whether one or more parts in the order have been recalled for some deficiency, whether parts in the order have been selected to be shipped by a particular shipping method, whether the price agreed upon by the user and the preferred provider is a special promotion that is offered only by the first provider, whether a price for the order includes a particular gross profit margin, as well as other attributes. 
     If it is determined at step  306  that the order is not routable, then at a step  308  the first provider must fulfill the order and the logic flow ends at step  310 . In other words, if the order is not routable, completion of the sale is undertaken with the first provider. 
     If it is determined at step  306  that the order is routable, then at step  312  a determination is made regarding whether the user has chosen to allow routing of the order. If the user has chosen to disallow routing of the order, then the methodology proceeds to step  308  where the first provider fulfills the order. 
     If, however, at step  312  the user has selected to allow routing of the order to occur, at step  314  a clock is initialized and the order is routed to the first provider. In an example, the order can be routed in one or more of a plurality of different routing techniques. For instance, the first provider can have client side application instructions executing on system circuitry resident on the premises of the first provider, and such client side application instructions can be configured to illustrate to the first provider that an order has been received and can be committed to by the first provider. This may be done for example by providing outputs through a display or other output device associated with the system circuitry of the provider. In another example, an e-mail can be transmitted to an e-mail address corresponding to the first provider. In still yet another example, a text message can be transmitted to a phone number of a particular person at the first provider. In still yet another example, application instructions executing on mobile phone or other mobile device can be in communication with the system  101  described above, and such circuitry executing the application instructions can receive an indication that an order has been placed by a user, and that the first provider is able to commit to fulfilling such order. 
     At a step  316 , a determination is made regarding whether the first provider has committed to fulfill the order by providing a response indicative thereof from the system circuitry associated with the provider. If the first provider has committed to the order, then the first provider fulfills the order at step  308  and the logic flow ends at step  310 . If the first provider has not committed to the order, then at step  318  a determination is made regarding whether a threshold amount of time has passed. In other words, a value output by the clock is monitored and compared with a threshold value, and at step  318  a determination is made regarding whether such threshold amount of time has passed. In the meantime, in exemplary embodiments, reminders can be transmitted by the system router component circuitry to the first provider that remind the first provider that an exclusive right to commit to fulfilling the order of the user will expire in a threshold amount of time. These reminders can be text messages, emails, graphical indicia appearing on a particular graphical user interface, etc. If the threshold amount of time has not passed, then the logic flow  300  returns to step  316  where a determination is made regarding whether the first provider has committed to fulfilling the order. 
     Referring now to  FIG. 56 , if the threshold amount of time has been determined to have passed at step  318 , then at a step  320  a second provider is selected by the rules analyzer circuitry based at least in part upon a variety of attributes pertaining to the user and/or the second provider. These attributes can include a type of the provider (e.g., where the provider is a relatively large or small business), a stocking status of one or more parts in the order (e.g., whether such parts are backordered at the second provider), a geographic proximity of the second provider to the user, type of parts in the order, a source of parts in the order, a time zone of the user when the order was placed, a time zone of the second provider when the order was placed, and other stored rules that are utilized in making the determination. While the step  320  describes a second provider as being determined and selected, it is to be understood that several providers can be selected for routing of the order based at least in part upon one or more of the factors and rules described above. For the purposes of explanation, however, the description herein has been limited to the second provider. 
     At a step  322 , the order is routed to the second provider. For example, routing of the order to the second provider can occur in a substantially similar manner as when the order was routed to the first provider. That is, an application instructions executing on a client side system circuitry of the second provider can be updated to provide one or more outputs indicate to the second provider that the second provider can commit to fulfilling the order of the user. Communications to the system circuitry associated with the second provider may be sent by the router component circuitry in the form of E-mails, text messages, or other message types. 
     At a step  324 , a determination is made by the order routing circuitry regarding whether or not a provider that has been provided with the order has committed to fulfilling the order. If it is determined that no provider has committed to the order, then at a step  326  a determination is made regarding whether a second threshold amount of time has passed. If the second threshold amount of time has not passed, then the logic flow  300  returns to step  324  where a determination is made regarding whether one of the providers that has received the order has committed to fulfilling the order. If the second threshold amount of time has passed, then at a step  328 , the circuitry operates to have a third provider automatically commit to fulfilling the order. In an example, the third provider can be a parent manufacturer, wholesaler or other entity. While the logic flow  300  has been shown as including review of two time thresholds, as indicated above, it can be understood that the logic flow carried out by the system circuitry may be adapted to include any suitable number of time thresholds, wherein additional providers are selected and the order is transmitted to the additional providers after passage of the threshold amounts of time. Accordingly, providers can be selected in “waves”, as previously discussed, and the order can be transmitted to the providers as the providers are selected. 
     If at step  324  it is determined that the order has been committed to by the first or second provider, then the logic flow  300  proceeds to a step  330  where a determination is made responsive to operation of the order finalizer component circuitry regarding whether a change in the price to the user may have occurred due to, for instance, changes in shipping cost, changes in sales tax applied to the price, etc. If it has been determined that there has been no price change at step  330 , then at step  332  the remote circuitry associated with either the first or second provider receives one or more messages directing the provider to fulfill the order. If at step  330  a determination is made that the price charged to the user has been altered due to changes in shipping price or changes in sales tax rates, then at step  334  the price is adjusted so that the total price originally agreed to be paid by the user is unchanged. In another example, if the price change is determined by the circuitry to cause a reduction in price, then such reduction is passed on to the user. The logic flow  300  then proceeds to a step  336  where the second provider receives messages that direct the provider to fulfill the order. The logic flow  300  then completes at a step  338 . 
     Referring now to  FIG. 57 , an exemplary graphical user interface  500  that can be presented to the user is illustrated. The graphical user interface  500  comprises a window  502  that is output on a display associated with the system circuitry associated with the user that includes indicia that corresponds to a description of order routing. Such description of order routing can inform the user that if the preferred provider does not commit to fulfilling the order in a timely manner, the order will be referred to other providers to provide such providers an opportunity to commit to fulfilling the order at no additional cost to the user. This window  502  can be provided to the user if the order desirably placed by the user qualifies for the option of order routing. The graphical user interface  500  may further include a first input selection element such as a checkbox  504  that can be selected by the user to indicate that the user wishes to have the order routed to other providers if the preferred provider fails to commit to fulfilling the order in a particular amount of time. The graphical user interface  500  can also comprise a second input selection element such as a checkbox  506  that is selectable by the user using an input device, such as a mouse or touch screen, to indicate that the user has read and understands appropriate terms and conditions of the order routing program. Furthermore, the graphical user interface  500  can comprise a selectable button  508 , wherein selection of such button  508  via an input device can place the order of the user (whether or not the first checkbox  504  has been selected by the user). The placing of such order, for example, can cause an authorization to be placed on the credit card or other account of the user by or on behalf of the preferred provider of the user for the price of the order placed by such user. 
     Now referring to  FIG. 58 , an exemplary graphical user interface  600  that can be provided through a display device of system circuitry of the provider is illustrated. The user interface is produced responsive to communication with the router component circuitry. The graphical user interface  600  can comprise a first field  602  that indicates particular order information, wherein the order information comprises indicia that indicates to the provider that the provider can commit to fulfilling at least one order. The graphical user interface  600  additionally comprises a second field  604  that includes indicia that provides time information to the provider. This time information can indicate when an order that may be committed to by the provider is set to expire and become available to other providers and/or will be auto-committed by a particular provider. If several orders are available to be committed to by the provider, the time information  604  for instance can display indicia corresponding to an amount of time that a soonest to expire order can be committed to by the provider. 
     Referring now to  FIG. 59 , another exemplary graphical user interface  700  that can be presented to a provider is illustrated. For instance, the graphical user interface  700  can be presented to the provider subsequent to the user providing an input through an input device selecting a button corresponding to the order information  602  shown in the graphical user interface  600 . The graphical user interface  700  comprises indicia corresponding to a table  702  that includes order information for one or more orders. In the exemplary graphical user interface  700  four orders are shown in the table  702 . In a first column  704  of the exemplary table  702 , indicia corresponding to order information can be presented to the provider. This order information may comprise time that the order was submitted, parts included in the order, and other order related indicia. A second column  706  in the table  702  includes indicia that indicates to the provider an amount of time remaining that the provider has to commit to the order shown in the column  704 . For instance, an order shown at the top of the table  702  may have a least amount of time remaining to commit to such order. Furthermore, graphical indicia can be provided in one or more entries of the table to inform the provider of other attributes pertaining to the order. For example, for the first order, the time entry corresponding thereto can be shaded a particular color to indicate to the provider that other providers are able to commit to fulfilling such order. Furthermore, as shown with respect to the second order, third order, and fourth order, graphical indicia  708 ,  710 , and  712  can be provided to the provider to indicate that the provider has the exclusive ability to commit to such orders, respectively, within the times corresponding to the indicia in the column  706 . The exemplary table  702  may comprise a third column  713  that identifies the user that placed the order. 
     The exemplary graphical user interface  700  can further comprise a first field  714  that provides a provider with detailed information pertaining to the order. Such information can include identities of repair parts in the order, quantities of parts in the order and price of respective parts in the order. 
     The exemplary graphical user interface  700  may also include a second field  716  that shows indicia corresponding to price information pertaining to the order shown in the first field  714 . This price information can include for example, a tax, a total price of parts in the order, an amount of tax that is to be applied to the parts in the order, a cost for shipping the parts in the order to the user, other fees that may be applicable to the order, any discounts that may be applicable to the order, and a total price corresponding to the order. The second field  716  may have at least one selectable button  718  therein that can be selected by in input through an input device associated with the provider system circuitry, an input corresponding to selection of such button commits the provider to fulfilling the order described in the fields  714  and  716 . 
     Now referring to  FIG. 60 , there is shown a high-level illustration of exemplary system circuitry  800  that can be used in accordance with the systems and logic flow descriptions herein. For instance, the exemplary circuitry  800  may be used in a system that supports placing an order for a particular part by a user. In another example, at least a portion of the circuitry  800  may be used in a system that supports automatic routing of orders to providers. The exemplary circuitry may  800  include at least one processor  802  like those previously described that executes instructions that are stored in a data store such as memory  804 . The memory  804  may include RAM, ROM, EEPROM, Flash memory, or other suitable memory. The instructions may include for instance, instructions for implementing functionality described as being carried out by one or more components discussed above or instructions for implementing one or more of the methods described above. The processor  802  may access the memory  804  by way of a system bus  806 . In addition to storing executable instructions, the memory  804  may also store rules, user attributes, provider attributes, user account data, parts pricing data, parts stocking data, tax data, shipping data and other data useful in accomplishing the described functions. 
     The exemplary system circuitry  800  additionally includes a data store  808  that is accessible by the processor  802  by way of the system bus  806 . The data store  808  may be or include any suitable computer-readable storage, including a hard disk, solid state, memory, or other machine readable medium. The data store  808  may include executable instructions, one or more rules, user attributes, etc. The exemplary system circuitry  800  also includes communication interface  810  that allows external devices to communicate with the system circuitry  800 . For instance, the interface  810  may be used to receive instructions from external circuitry operated by a user or other entity. The exemplary system circuitry  800  also includes a device interface  812  that interfaces the system circuitry  800  with one or more external devices. For example, the system circuitry  800  may communicate with a display or other output device such as a printer to output text, images, and other indicia by way of the device interface  812 . Device interface  812  in exemplary embodiments may also interface with input devices. Such input devices may include for example, a mouse, keyboard, touch screen, biometric reader or an audio input device. 
     Additionally, while illustrated as a single system, it is to be understood that the system circuitry  800  may be a distributed system. Thus, for instance, several devices may be in communication by way of a network connection and may collectively perform tasks described as being performed by the system circuitry  800 . 
     As used herein, the terms “component” and “system” are intended to encompass hardware, software, or a combination of hardware and software. Thus, for example, a system or component may include a process or a process executing in circuitry. Additionally, a component or system may be localized on a single device or distributed across several devices. Furthermore, a component or system may also refer to stored data and instructions stored in a portion of machine readable memory. 
     Thus the system controlled responsive to data bearing records of exemplary embodiments achieves useful results, eliminates difficulties encountered in the use of existing system and attains the useful and beneficial results described herein. 
     In the foregoing description certain terms have been used in connection with describing exemplary embodiments for purposes of brevity, clarity and understanding. However, no unnecessary limitations are to be implied therefrom because such terms are used for descriptive purposes and are intended to be broadly construed. Moreover the descriptions and illustrations herein are by way of examples and the new and useful concepts are not limited to the features that are shown and described. 
     Further in the following claims any feature described as a means for performing a function shall be construed as encompassing any means known to those skilled in the art as being capable of carrying out the recited function and shall not be deemed limited to the particular means shown or described for performing the recited function in the foregoing description or mere equivalents thereof. 
     Having described the features, discoveries and principles utilized in the exemplary embodiments, the manner in which they are constructed and operated and the advantages and useful results attained, the new and useful structures, devices, elements, arrangements, parts, combinations, systems, equipment, operations and methods, processes and relationships are set forth in the appended claims.